Infrastructure
The infrastructure behind the experience
When the sensors say an app is slow from every office at once, the next question is whether the server behind it is struggling. That answer is in the same portal, on the same timeline.
What the server agent watches
A lightweight agent on each Linux or Windows server or VM reports outbound to your Cloud Unit.
Linux and Windows servers
CPU, memory, disk and network every 20–30 seconds.
Critical processes
An alert the moment a named process disappears, such as a security agent or a connector.
Apps and certificates
Endpoint availability, and the days left before each certificate expires.
Containers and platforms
Docker metrics. AWS, Azure, VMware, Hyper-V and Google Cloud Platform recognised.
Single pane of glass
Your whole estate, next to your users
Windows and Linux servers across your clouds, with instance type and free memory, CPU and disk, plus the containers running on them. One view for the service as users consume it and the servers that deliver it.
Add cloud-provider monitoring to see the provider's own services through its API, for AWS, Azure and Google Cloud Platform. Priced on request.
Agents that look after themselves
Self-updating
Agents keep themselves up to date. New versions are proved on reference servers before your whole estate takes them.
Safe configuration changes
Agents check a new configuration before applying it, and you change what is monitored in the portal, not on servers.
Alerts that build themselves
Set thresholds for CPU, memory, disk, missing processes and certificate expiry in simple forms. Alerting.
Metrics, not logs or traces. CNA sits alongside your logging and APM tools. It adds the one view they can't give: the service as users consume it, next to the servers that deliver it.
Prove it on your own network
Six weeks, your most-complained-about office, the apps your people can't work without, and success criteria you agree up front.