User guide
RMM Integrations
Looking for what it does rather than how to use it? Read the RMM Integrations overview .
Audience: MSP administrators connecting remote monitoring and management tools. Scope: ConnectWise Automate, Zabbix, ConnectWise ScreenConnect and Azure Resource Manager — discovery, alerting, remote actions and monitoring settings.
What it is
Solidlio connects to your RMM and monitoring tools, imports the devices they manage as assets, ingests their alerts, and — for Automate and ScreenConnect — lets technicians act on a machine without leaving the ticket.
Four providers ship. Datto RMM and NinjaOne appear in the catalogue as Coming Soon and cannot be connected; there is no implementation behind them.
| Provider | What it gives you |
|---|---|
| ConnectWise Automate | Device inventory, software, drives, patches, alerts, live remote actions |
| Zabbix | Host discovery, alert ingestion, maintenance-window push |
| ScreenConnect | Session discovery, remote control, wake, message, lock, support sessions |
| Azure Resource Manager | Cloud resource inventory, decommission detection, cost ingestion |
Concepts
| Concept | What it is |
|---|---|
Integration | One connection to one RMM server, holding encrypted credentials. |
IntegrationMapping | Pairs an RMM device id with a Solidlio asset, scoped to that integration. |
| Client / group mapping | Automate clients or groups → Solidlio organizations. Decides which tenant a device lands in. |
| Host-group mapping | Zabbix host groups → Solidlio organizations, with per-host overrides. |
AssetMonitoring | Per-asset, per-source monitoring state: status, last check, and collected metrics. |
MonitoringAlert | One alert, tenant-pinned, deduplicated per source and external id. |
MonitoringConfig | Per-organization monitoring settings, including the Automate alert cadence. |
Roles and permissions
Config and hosts are floored because they return server URLs, client ids and unmapped inventory. Alerts and status are left open because they are statements about the caller’s own machines and are what the customer portal renders.
Walkthrough — ConnectWise Automate
- Gather credentials — your Automate server URL, the Partner Client ID GUID from the ConnectWise Developer portal, and an Automate login. This is not an OAuth2 client id/secret pair.
- Connect —
Integrations → ConnectWise Automate(MSP portal). - Map clients to organizations — each Automate client, or group, to a Solidlio organization. Unmapped devices are never invented into a tenant.
- Choose what syncs — computers, software, services, drives, patches, groups, clients and locations each have a toggle, and computer, software and full-sync cadences are settable.
- Watch alerts become tickets — alerts are ingested on a schedule, deduplicated onto an already-open ticket where one exists, and suppressed during a maintenance window.
Automate is an MSP-portal integration. The organization portal redirects to it rather than offering a second, non-functional copy.
Remote actions
From an asset or a ticket, a technician can run a command or script, reboot, or shut down a machine. Every action requires organization administrator and writes an audit record.
Walkthrough — Zabbix
- Connect — server URL and an API token. Solidlio detects your Zabbix version and uses the Bearer header on 6.4+ (the
authbody property was removed in 7.2) or the legacy transport below that, recovering automatically if it guesses wrong. - Map host groups — Zabbix host groups to Solidlio organizations, with per-host overrides where a group spans customers.
- Enable syncs — host and alert syncs each have their own toggle and interval. A connection made through the API rather than the wizard is now scheduled with sensible defaults rather than silently doing nothing.
- Optionally add the inbound webhook — for push alerting rather than polling. The secret is shown when minted or rotated.
- Maintenance windows — a maintenance window scheduled in Change Management is pushed to Zabbix so alerts are suppressed for its duration.
Walkthrough — ScreenConnect and Azure
ScreenConnect — connect with your instance URL and credentials, then link sessions to assets. Remote control, wake, message, lock and ad-hoc support sessions become available from the asset list, the asset detail page and the ticket detail page. Launch URLs are restricted to sessions your integration actually knows about, and every launch is audited.
Azure Resource Manager — connect by granting admin consent to Solidlio’s Entra application against your tenant. Resources are imported as assets, refreshed on change, and marked decommissioned when they disappear. Cost Management data is ingested separately.
Troubleshooting
| What you see | Cause |
|---|---|
| Automate connect fails immediately | Missing partner Client ID. Solidlio refuses to connect without one. |
| Automate asks for a client secret | You are reading stale documentation — the real auth is Client ID + username/password. |
| Zabbix connects but nothing syncs | Enable the host and alert syncs; a connection with no sync config schedules nothing. |
| Zabbix alerts land on the wrong asset | Two Zabbix servers mapped into one organization. Host ids collide; mappings now disambiguate. |
| ScreenConnect says “incomplete credentials” | Fixed. This affected every real install; reconnect if it persists. |
| Azure VM shows no CPU or storage | Fixed. Re-run a sync to populate. |
| Azure resources all land in the MSP’s own org | Expected — see limits below. |
| A sync shows “Unknown error” | Fixed; the real message is now recorded. |
| Sync history shows a successful run that failed | Fixed for Azure; failures are now recorded as failures and retried. |
Limits and known behaviour
- Datto RMM and NinjaOne are not implemented. They cannot be connected.
- Azure has no subscription-to-client mapping. Unlike Zabbix host groups and Automate clients, every Azure resource lands in the connecting organization. An MSP cannot yet attribute Azure resources to individual clients.
- Automate stores total storage across all volumes, with the primary volume’s type. Per-volume detail is available live on the device page, not on the asset.
- ScreenConnect has no dedicated management page; it is configured through the generic setup wizard and surfaced on asset and ticket pages.
- RMM and monitoring integrations are not plan-gated — every tier includes them.