Edge Server Status Monitoring
This is where an overview of Edge server statuses are displayed as a simplified report that is updated once every ten minutes.
Passive Monitoring Columns Overview
Active Monitoring | Shows current status of active monitoring. For an explanation, refer to the section below this table. |
Passive Monitoring | Shows current status of passive monitoring. |
Edge Status | Shows whether the Edge server is active and available to serve or not. |
Edge timestamp status | Shows the status of the time service within the Edge server. |
Network Utilization | Checks how much of the network has been used. The rate is now measured in Mbps or megabits per second. |
CPU IO Wait | The approximate percentage of the time that the system was idle and at least one process was waiting for Linux disk IO to finish. The actual kernel measure is the amount of time that each CPU has spent in each mode. Not all IO causes processes to wait. For example, Linux doesn't immediately flush data written to files to disk; it does it later, in the background, when it's convenient. A increasing IO wait is a danger sign that the server may be go into an IO bottleneck. Low IO wait is not necessarily an indication that there are no IO problems. |
1/5/15 min load | This is the standard UNIX load average. It measures the number of active processes, for the past 1, 5, and 15 minutes, hence its name. This load isn't CPU utilization, but the process queue length. |
Last checked | Approximate days ago when this monitor was last obtained. |
Active Monitoring Status
Overview:
Active Probes are performed to check if the services exposed on the surrogates are actually publicly accessible.
Availability:
Service is considered available if the last probe by at least one prober returns success.
In the database, the metric for activemon is based on exit codes. ie a 0 indicates the probe is successful and service is available. A 1 indicates a general error. These codes can be extended to map to different definitions.
