One list, every plan.
These devices, vendors and telemetry types are supported the same way on all four plans. The plans differ in who is on-site and when, not in what we can monitor.
What we cover.
Network
- Core, distribution and access switches
- Routers and SD-WAN edges
- Load balancers
Security edge
- Firewalls and UTMs
- Site-to-site and remote-access VPNs
- Health and HA state only, not threat monitoring
Connectivity
- Internet and WAN links
- MPLS and leased lines
- ISP circuits and their SLAs
Servers and virtualisation
- Windows Server and Linux
- VMware vSphere and Microsoft Hyper-V hosts
- Physical server hardware (add-on)
Storage
- NAS units
- Volume capacity and disk health where reported
Applications and services
- Websites, web apps and ERP portals
- Email gateways, DNS, SSL certificates
- Key TCP services such as SMTP and RDP
Wireless
- Wi-Fi controllers and cloud-managed Wi-Fi
- Access points and client counts
Power and environment
- UPS units with a network card
- PDUs and room temperature sensors
Cloud and SaaS
- Microsoft 365, Google Workspace
- Hosted apps, checked from outside
- AWS, Azure, GCP metrics (add-on)
Not covered
- Staff laptops, desktops and phones
- Printers and CCTV cameras
- Security monitoring (SOC)
- Industrial and building systems
Vendors we work with.
Any device that supports SNMP v2c or v3, our agent, or a read-only API can usually be monitored, even if its vendor isn't listed. We confirm every device during discovery.
| Vendor | Devices | How we monitor | AI read-only checks |
|---|---|---|---|
| Fortinet | FortiGate, FortiSwitch, FortiAP | SNMP v3REST API | Available |
| Cisco | Catalyst, ISR, ASA, Firepower, Meraki | SNMP v3Meraki API | Available |
| Palo Alto Networks | PA-Series firewalls | SNMP v3XML API | Available |
| Sophos | XGS / XG firewalls | SNMP v3API | Available |
| HPE Aruba | Aruba CX and ProCurve switches, Aruba APs and controllers, Aruba Central | SNMP v3REST API | Available |
| Juniper | EX switches, SRX firewalls, Mist | SNMP v3API | Available |
| Huawei | CloudEngine and S-series switches, AR routers, USG firewalls | SNMP v3 | Available |
| MikroTik | RouterOS routers and switches | SNMP v3API | Available |
| Ubiquiti | UniFi gateways, switches and APs | SNMPUniFi API | On request |
| Ruckus | SmartZone controllers, ICX switches | SNMP v3 | On request |
| TP-Link | Omada switches and APs | SNMP | On request |
| Microsoft | Windows Server, Hyper-V | AgentWMI | Available |
| Linux | Red Hat, Rocky, AlmaLinux, Ubuntu, Debian | AgentSSH | Available |
| VMware (Broadcom) | vSphere ESXi hosts, vCenter | vSphere API | On request |
| Dell, HPE, Lenovo | PowerEdge, ProLiant, ThinkSystem servers | Agent on the OSIPMI / Redfish add-on | On request |
| Synology, QNAP | NAS units | SNMP | Not available |
| APC, Eaton, Vertiv | UPS units and PDUs with a network card | SNMP | Not available |
| Microsoft 365, Google Workspace | Email and collaboration | HTTPS checksProvider status | Not available |
AI read-only checks: "Available" means we have an approved command list for that vendor. "On request" means we build one during onboarding. "Not available" means the device offers no suitable read-only login, so AI works from monitoring data only. Product names are trademarks of their owners; listing them doesn't imply a partnership.
Exactly what we watch.
The 50 included devices can be any mix of the classes below. Intervals are how often we check. A problem that starts and clears between two checks may not be seen.
| Device or service | What we watch | Protocol | Check interval |
|---|---|---|---|
| Switches & routers | Reachable, interface up/down, bandwidth in/out, errors and discards, CPU, memory, reboots, temperature, fan and power supply where the device reports them | ICMPSNMP v3 / v2c | Ping 1 min · SNMP 5 min |
| Firewalls | Reachable, HA state, CPU, memory, session count, interface status, VPN tunnel status where the vendor exposes it | ICMPSNMP v3Vendor API (read-only) | Ping 1 min · SNMP 5 min |
| Internet & WAN links | Up/down, latency, packet loss, jitter, utilisation on your edge interface | ICMPSNMP | 1 min |
| Windows & Linux servers | Reachable, CPU, memory, disk space per volume, named services and processes running, reboots | Monitoring agentSNMPWMI | 1–5 min |
| Websites & web apps | HTTP status, response time, expected text on the page, SSL certificate expiry (warned 30 days ahead) | HTTPS check | 1–5 min |
| Wireless | Controller health, access point up/down, connected clients per AP | SNMP via controller | 5 min |
| UPS & environment | On battery, battery charge, load, runtime left, room temperature | SNMP (network card needed) | 5 min |
| Device logs | Critical events from network devices, such as link flaps, power supply failure or config saved | Syslog | As received |
Data kept: detailed readings for 90 days, hourly trends for 13 months.
What we can take in, and what we can't.
If a data source isn't on this list as included, our plans don't cover it. Add-ons are quoted separately.
| Telemetry | All plans | Notes |
|---|---|---|
| ICMP ping | Included | Up/down, latency, packet loss, jitter. |
| SNMP v3 polling (authPriv) | Included | Preferred for all network devices. |
| SNMP v2c polling | Included | Read-only community, on a management network only. |
| SNMP traps (v2c, v3) | Included | Sent by your devices to the on-site collector. |
| Syslog | Included | UDP 514, TCP 514 or TLS 6514; RFC 3164 and 5424. Network devices and firewalls; filtered for operational faults. |
| Monitoring agent metrics | Included | Windows and Linux servers. See agent options below. |
| WMI (Windows) | Included | Agentless option, read-only account. |
| SSH read-only checks (Linux) | Included | Agentless option for Linux, key-based, restricted user. |
| HTTP/HTTPS checks | Included | Status, response time, page content, SSL expiry. Run from our hub and from your collector. |
| TCP port and DNS checks | Included | Service reachability (for example SMTP 25, RDP 3389) and DNS resolution. |
| Vendor REST APIs (read-only) | Included | Where the vendor offers one, such as firewall and Wi-Fi controllers. Read-only API key. |
| Read-only diagnostic logins (AI checks) | Included, opt-in | SSH or vendor API from your collector, read-only account, approved commands only. Used when a threshold or anomaly triggers. |
| Windows Event Log | Limited | Critical and error events for named services only, through the agent. |
| NetFlow, sFlow, IPFIX | Add-on | Bandwidth by application, user or destination. |
| IPMI / Redfish (server hardware) | Add-on | Out-of-band hardware health: disks, fans, power supplies. |
| Cloud provider metrics (AWS, Azure, GCP) | Add-on | Through the provider's monitoring API. |
| SNMP v1 | Not supported | No authentication and no encryption. Upgrade to v2c or v3. |
| SNMP write (SET) | Not supported | We never change device settings through monitoring. |
| Packet capture, SPAN or port mirroring | Not supported | We don't collect traffic content. |
| Streaming telemetry (gNMI, gRPC) | Not supported | We poll by SNMP or API instead. |
| Application tracing (APM, OpenTelemetry traces) | Not supported | We check that applications respond, not how their code performs. |
| Security logs (SIEM feeds, EDR, IDS alerts) | Not supported | Security monitoring is a SOC service, not a NOC service. |
| Staff laptops, desktops and phones | Not supported | End-user devices stay with your helpdesk. |
| Industrial protocols (Modbus, BACnet, DNP3) | Not supported | Building and plant systems are outside our scope. |
Agentless for the network. Your choice for servers.
The only thing you must install is one collector. Switches, firewalls, links, Wi-Fi and UPS are always agentless. For servers you choose between our agent and agentless monitoring.
| What | Agent needed? | Who installs it | What it needs on your side |
|---|---|---|---|
| Monitoring collector | Required, one per site | You host a small VM and we install the collector, or we ship a mini appliance | 2 vCPU, 4 GB RAM, 50 GB disk. Outbound TCP 443 to our hub. No inbound ports. |
| Switches, routers, firewalls | Agentless | Nothing to install | SNMP v3 user (or v2c read-only community), syslog pointed at the collector |
| Internet and WAN links | Agentless | Nothing to install | Circuit details and the edge interface name |
| Wi-Fi, UPS, controllers | Agentless | Nothing to install | SNMP or a read-only API key |
| AI diagnostic access (optional) | Agentless | Your IT team creates the accounts; we load them into the collector's vault | A read-only SSH or API account on each network device you want AI to check. Without it, AI works from monitoring data only. |
| Websites and web apps | Agentless | Nothing to install | The URLs and the text we should expect on each page |
| Windows and Linux servers | Agent recommended or agentless | Your IT team, using our installer and guide. Or you give us temporary access during onboarding and we do it. | Agent: open-source Zabbix agent 2, under 50 MB RAM, talks only to the collector inside your network. Agentless: a read-only WMI account (Windows) or restricted SSH key (Linux). |
Why we recommend the agent
It sees more (per-process memory, service status, event log errors), checks more often, and keeps working when the network is busy. It sends data out to the collector, so no server ports open to us.
When agentless is better
Your policy forbids third-party software on servers, or the server belongs to a vendor who won't allow it. You'll get CPU, memory, disk and service status, checked every 5 minutes instead of every minute.
Removing it later
When the contract ends we give you the uninstall steps, remove our accounts and SNMP users, and confirm in writing that our access is closed.
Also needed from you
- Contacts and vendor detailsYour on-call contacts, ISP circuit IDs and vendor support contracts, so we can log faults on your behalf.
- A maintenance calendarTell us about planned work so we pause alerts instead of escalating them.
Send us your device list and we'll confirm coverage.
We'll tell you which devices get full monitoring, which are ping-only, and which can have AI checks.
[email protected]