Monitoring and Alerting

The problem

Your monitoring server is doing its job. It has been emailing the whole technical team since 2019. Nobody can say which of last night’s forty alerts were for the same failing disk, which belonged to the client who is about to renew, or which of them anyone actually looked at. The maintenance window you scheduled for Saturday generated ninety alerts and three tickets, because the monitoring system was never told about it. And when a client asks how many outages they had last quarter, the honest answer is that it is in a mailbox somewhere.

What Solidlio does about it

Solidlio connects to your existing Zabbix and ConnectWise Automate servers and imports what they see. Each problem is placed against the customer that owns the alarming host — one Zabbix server can front fifty client companies, and the group mappings decide who gets what. Placed alerts attach to the Solidlio asset they concern, so an alert names a device rather than an id. Whether an alert becomes a ticket is a rule per client: a severity floor, a switch for merging repeats onto one ticket, a switch for closing the ticket when the problem clears, and suppression for anything inside a maintenance window. Acknowledge or resolve in Solidlio and it is acknowledged or resolved in Zabbix too.

Capabilities

Built for MSPs and their clients

Monitoring is where the two-sided model earns its keep: the MSP runs one Zabbix server for everybody, and each client still needs to see only its own estate.

An alert’s identity is (organization, source, external id). That matters because Zabbix event ids and Automate alert ids are only unique inside one server: two customers running their own Zabbix will both eventually emit event 12345, and Solidlio keeps them as two separate alerts belonging to two separate tenants.

How it works

1. Connect — enter the Zabbix API URL and token, or the Automate URL, username and password. Solidlio detects the server version and stores the credentials encrypted.
2. Map — assign each Zabbix host group, or each Automate client company, to the Solidlio organization that owns it.
3. Sync — hosts arrive on a schedule and resolve to existing assets by prior mapping, serial number, MAC address or hostname, creating one only when nothing plausibly matches. Alerts follow every few minutes.
4. Rule — set the severity floor, repeat merging, auto-resolve and maintenance suppression per client under Settings → Monitoring.
5. Work — the desk sees a cross-client list with severity, client, device and age. Acknowledge, resolve, or raise a ticket under the client’s organization with the asset already attached.
6. Close the loop — when the monitoring system stops reporting the problem, the alert resolves, and with auto-resolve on, so does the ticket.

Compliance and audit

Every alert is a durable record, not a mail. Reconstructable after the fact:

• Which organization and which asset the alert belonged to, and the source and external id it came from
• When it was triggered at the source, in the source’s own timestamp
• Who acknowledged it and when
• When it resolved, and whether by hand or because the source stopped reporting
• The ticket it raised, if any, and the tags identifying it as machine-generated
• Whether it was suppressed, and that a maintenance window was the reason
• The full source payload — host id, hostname, computer id, client name, alert type — retained as structured metadata

Maintenance windows record the external maintenance period id created in Zabbix, so a planned outage can be proved to have been declared to the monitoring system and not merely written down.

Editions

Monitoring carries no plan gate. Zabbix, ConnectWise Automate, alert ingestion, alert-to-ticket rules, host linking and maintenance suppression are available on every MSP and end-customer tier. Access is governed by role and tenancy only.

Integrations

Zabbix 6.0 through 7.x — hosts, host groups, problems, items, history, graphs, maintenance periods, and host enable/disable. Authentication uses an Authorization: Bearer header on 6.4 and later and falls back to the legacy body property on older servers, because the auth body property was removed in 7.2. An signed webhook address accepts pushed events.

ConnectWise Automate — computers, installed software, services, drives, patches and alerts, plus remote command execution, reboot, shutdown and script execution. Authentication is a Partner ClientId header with a username and password exchanged for an AccessToken.

Monitoring data also feeds Solidlio’s own asset records, ticket creation, and change-management maintenance windows.