Health Monitoring¶
Overview¶
The Health Monitoring section of the CMS portal provides real-time and historical performance metrics for each enrolled device. Administrators can use this data to track resource utilisation, identify performance trends, and proactively address issues before they affect end users.
Performance metrics¶
The following metrics are tracked continuously for each enrolled device:
| Metric | Unit | Description |
|---|---|---|
| CPU usage | % | Current processor load |
| Memory usage | % | Current RAM consumption |
| Disk usage | % | Current storage utilisation |
| Disk IOPS | Operations/sec | Read and write operations per second |
| Disk I/O throughput | MB/s | Data transfer rate to and from disk |
Historical monitoring¶
In addition to real-time data, CMS retains historical performance records for each device. Historical data enables administrators to:
- Identify usage trends over time
- Detect anomalies such as sustained high CPU or memory spikes
- Correlate performance degradation with software deployment events
- Support capacity planning and hardware refresh decisions
Key benefits¶
- Centralised visibility into device configuration and performance across the entire enrolled fleet
- Simplified troubleshooting using historical performance data without requiring physical access to the device
- Proactive identification of issues before they cause user-facing disruption
Use case
If an end user reports a slow or unresponsive device, the Health Monitoring view provides an immediate read on CPU, memory, and disk pressure — allowing the administrator to diagnose the issue remotely and determine whether the cause is resource contention, a failing disk, or a software process anomaly.