Monitoring the OLVM Manager 4.x

eG Enterprise provides a 100%, web-based OLVM Manager 4.x monitoring model, which periodically runs status and health checks on the OLVM Manager 4.x and proactively reports abnormalities.

Figure 1 : The layer model of the OLVM Manager 4.x

Each layer depicted by above figure is mapped to tests, which employ agentless mechanism to pull out a variety of metrics from the OLVM manager. The metrics so collected enable administrators to quickly find accurate answers to the following performance queries:

  • Is the OLVM Manager reachable over the network? If so, how quickly is it responding to requests?

  • Have any error or warning events been generated by the OLVM Manager recently? What are these errors or warnings?

  • Have any new errors or warnings been recorded in the OLVM Manager logs? If so, what are they?

  • How many datacenters are currently configured on the OLVM Manager? What is the status of each datacenter?

  • Is any datacenter currently in a problematic state? If so, which one?

  • How many clusters, hosts, and virtual machines are configured in each datacenter?

  • Is any datacenter running short of storage space? Which storage domains are affected, and how many clusters, hosts, and VMs are associated with them?

  • How many storage domains are configured in each datacenter, and how many of them are currently available?

  • Is any storage domain unavailable? If so, which one, and which virtual machines are dependent on it?

  • Is any storage domain running out of free space? Which one is it, and which virtual machines may be impacted?

  • Is any cluster experiencing high memory overcommitment or memory contention? If so, which cluster is affected?

  • Is memory ballooning enabled in all clusters? If not, which clusters have ballooning disabled?

  • Is any cluster using CPU resources excessively? If so, which cluster is affected?

  • Are there clusters with a large number of powered-off or suspended virtual machines? Which clusters are they?

  • How many hosts are currently operational in each cluster?

  • Is any host not operational or reporting low CPU or memory capacity?

  • Is any host running low on free memory required for scheduling new virtual machines?

  • Are there hosts with a high number of active or migrating virtual machines, indicating load imbalance?

  • Are there frequent migrations occurring on any host, suggesting resource pressure or instability?