Override IDs of ESXi metrics

For ESXi, currently Abiquo defines a set of metrics (PerfMetrics) to retrieve and it includes the expected ID (PerfMetricId)

However, the IDs of the metrics are dynamic and may change in some environments (for example, certain vCenter configurations), so Abiquo has created properties to override these metrics IDs in remote services for any specific datacenter.

 

Default ESXi metric mappings

The default metric mappings are given in the following table.

Metric

ID mapping

Metric

ID mapping

cpu

2

memory-physical

98

memory-swap

85

disk-latency

133

cpu-mz

6

memory-swap2

86

memory-host

102

memory

24

memory-vmmemctl

90

uptime

155

cpu-time

12

 

System properties to override metric IDs

To override these IDs, add system properties to Abiquo to override the IDs. On the Remote Services server, add them to the abiquo.properties file.

The property format is abiquo.esxi.metricsid.{METRIC}.

The METRICs are:

  • cpu

  • cpu-mz

  • cpu-time

  • memory

  • memory-swap

  • memory-swap2

  • memory-vmmemctl

  • memory-physical

  • memory-host

  • disk-latency

  • uptime

For each property, set a value to override the default metric ID as given in the table above.

 

Metrics override example

For example, to change the values of the cpu and uptime metric IDs, set the following:

abiquo.esxi.metricsid.cpu = 155 
abiquo.esxi.metricsid.uptime=2 

After restarting the environment, monitoring will display "cpu" values in the "uptime" graphic and "uptime" values in the "cpu" graphic. 

 

Determining metric IDs

Contact Abiquo Support for more information about how to obtain the dynamic metric IDs.

 

Copyright © 2006-2024, Abiquo Holdings SL. All rights reserved