Abiquo 5.1

Skip to end of metadata
Go to start of metadata

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.

MetricID mapping
cpu2
memory-physical98
memory-swap85
disk-latency133
cpu-mz6
memory-swap286
memory-host102
memory24
memory-vmmemctl90
uptime155
cpu-time12

System properties to override metric IDs

To override these IDs, add system properties to Abiquo to override the IDs

MetricDescriptionAPIRSV2VOAInfo

abiquo.esxi.metricsid.{METRIC}

    • cpu
    • cpu-mz
    • cpu-time
    • memory
    • memory-swap
    • memory-swap2
    • memory-vmmemctl
    • memory-physical
    • memory-host
    • disk-latency
    • uptime
For ESXi, to support dynamic metric IDs, set a value to override the default metric ID as given in the table in Abiquo documentation

    

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.

  • No labels