Some IOPS data is missing from the Console Grid (N\A)

The Issue:

Some of the performance metric columns show N\A, such as “Dropped Received Packets” or "CPU Ready".

The Controlup Real Time Grid present performance information collected both from the agent and from the hypervisor (agentless).

These columns are retrieved from the hypervisor.

 

The Solution:

 If you are not connected to the hypervisor, the performance metric columns will show no data, in black & white N\A. See this page for details on how to configure hypervisor connections.

If you are connected, the columns will show up in Green, but if the data is not presented and instead you have N\A, it means that you need to enable those performance metrics on the hypervisors.

Your VMs are hosted on XenServer, then there are specific performance counter commands that may need to be issued on the poolmaster to enable the counters at the host and VM level.

First, you need to know that IOPS data is supported starting XenServer 6.1 (In case your host is Xenserver).

You need to explicitly enable the IOPS metrics by running the following command on the host - "xe-enable-all-plugin-metrics true"

For more host-level monitoring information, see this page in the online documentation.

For more VM-level monitoring information, see the following commands:

Network stats:
Dropped received packets: Run "xe vm-data-source-record data-source=vif_0_rx_errors uuid=<vm-uuid>" to enable for each NIC to track (eth0, eth1, etc).
Dropped transmitted packets: Run "xe vm-data-source-record data-source=vif_0_tx_errors uuid=<vm-uuid>" to enable for each NIC to track (eth0, eth1, etc).

Disk stats:
Read IOPS: "xe vm-data-source-record data-source=vbd_hda_iops_read uuid=<vm-uuid>" to enable for each VBD to track (hda, hdb, etc)
Write IOPS: "xe vm-data-source-record data-source=vbd_hda_iops_write uuid=<vm-uuid>" to enable for each VBD to track (hda, hdb, etc)
Read latency: "xe vm-data-source-record data-source=vbd_hda_read_latency uuid=<vm-uuid>" to enable for each VBD to track (hda, hdb, etc).
Write latency: "xe vm-data-source-record data-source=vbd_hda_write_latency uuid=<vm-uuid>" to enable for each VBD to track (hda, hdb, etc).

** The VBD needs to be a real disk/VDI, not PVS write cache or ISO VDI

 

 

 

Powered by Zendesk