Clusters. The number of all clusters associated with the virtual center, followed by the total counts of alarms associated with the clusters, broken down by alarm types (Normal, Warning, Critical, Fatal).
•
CPU. The current percentage of the overall virtual center’s CPU load, used to execute system code and user programs, based on the total CPU capacity.
•
Datacenters. The number of all datacenters associated with the virtual center, followed by the total counts of alarms associated with the datacenters, broken down by alarm types (Normal, Warning, Critical, Fatal).
•
Disk. The overall datacenter’s current disk I/O rate.
•
Hosts. The number of all hosts associated with the datacenter, including running and turned-off hosts.
•
Memory. The current percentage of the virtual center’s memory usage.
•
Network. The current rate at which the virtual center transfers data from and to the network.
•
Virtual center. The name of the virtual center, followed by the total counts of alarms associated with the virtual center, broken down by alarm types (Normal, Warning, Critical, Fatal).
•
VMs. The number of all virtual machines associated with the virtual center, including running and powered-off virtual machines.
Foglight Agent Manager Host. The name of the machine on which the Agent Manager and the VMware Performance Agent process are running.
•
Metric History. The progress of the import of historical data. Each VMware Performance Agent monitors a single Virtual Center. When you create a VMware Performance Agent instance and the Agent Setup wizard determines that the Virtual Center was not previously monitored by this Foglight instance, it starts importing historical data into Foglight. This data is not immediately available as it takes some time to collect it. This process can import data collected over 30 days or less, depending on the amount of data available in the Virtual Center. This allows you to explore VMware metrics as soon as the data is imported, instead for waiting for the agent to collect some data from the Virtual Center. Historical data is intended for charting, trending, and general presentation purposes. It does not cause any alarms to fire.
Click this column to start a metric history import, or to see its progress. When the import is in progress, you have an option to cancel it, if needed. Click Cancel in the dwell to cancel the import. You can resume it at a later time.
When the metric history import is completed, this is indicated in the dwell.
), or it needs to be updated (
).
