Service · Monitoring & alerting
See it before your users do, and keep the evidence.
Zabbix, Wazuh and Tactical RMM feeding one ticket queue, priority-1 (P1) paging for servers that go dark, and a public status page per client.
Ask about monitoringWhat's included
- Server and network monitoring (Zabbix) with per-client host groups and monthly compliance exports.
- Security information and event management (SIEM) alerts from Wazuh.
- Endpoint health from Tactical RMM.
- Alert-to-ticket automation into HaloPSA with recovery notes.
- A client-branded status page.
- Disaster-recovery (DR) monitoring that watches the primary site from the DR site, so an outage cannot silence its own alarm.
What you can expect
Response targets
These are the response targets in our standard agreement. They are targets, not a signed service-level agreement (SLA): the terms that apply to you are the ones in your contract. Business hours are Monday to Friday, 09:00–18:00.
| Priority | Definition | Response | Resolution target |
|---|---|---|---|
| P1 Critical | Business operations halted (email down, ransomware in progress, directory outage) | 1 business hour | 4 business hours |
| P2 High | One significant function affected (a server down, one team cannot work) | 4 business hours | 1 business day |
| P3 Normal | Single user or non-critical issue | 1 business day | 3 business days |
| P4 Low | Information or change requests | 2 business days | 5 business days |
Critical incidents out of hours are covered by agreement in your contract.
Tools we run
Zabbix
Wazuh
Tactical RMM
Uptime Kuma
Grafana
Loki
HaloPSA
n8n
Tell us what isn't working.
A 30-minute call, no slides. We ask about your estate, your auditor if you have one, and what you would like to stop worrying about.
Ask about monitoring