VMware collector support for units and value modifier

Description

The raw metrics provided from the VMware API can't be used directly. Each measurement has meta information such as a value modifier and the unit. To collect the metrics correctly the value modifier and the unit need to be collected as well and taken into account when stored in the timer series storage in OpenNMS to be useful.

See https://www.vmware.com/support/developer/converter-sdk/conv61_apireference/vim.PerformanceManager.html

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger April 7, 2017 at 12:52 PM

Merged the rebased branch to foundation-2017. Marking as fixed.

commit 7cc4e7320352944ffa90359b0315d92718b88d5d

Seth Leger April 5, 2017 at 12:33 PM

Is there any reason that these changes can't go into foundation-2017? I've created a new branch with the changes rebased against foundation-2017.

https://github.com/OpenNMS/opennms/tree/jira/NMS-9092-foundation2017

Ronny Trommer February 9, 2017 at 6:24 AM

Suggestion to fix provided in PR: https://github.com/OpenNMS/opennms/pull/1283

Fixed

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created February 9, 2017 at 6:15 AM
Updated April 7, 2017 at 4:48 PM
Resolved April 7, 2017 at 12:52 PM