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 |
|---|---|
| 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
| Metric | Description | API | RS | V2V | OA | Info |
|---|---|---|---|---|---|---|
abiquo.esxi.metricsid.{METRIC}
| For ESXi, to support dynamic metric IDs, set a value to override the default metric ID as given in the table in Abiquo documentation |  |
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.