Metric Identifiers - HP HPE VAN SDN Controller 2.7 Administrator's Manual

For metric values that are exposed via JMX:
The metric value reported by JMX is the most recently-reported raw value. The value does
not include time interval information or any normalization data such as accrual rate. For
example, for a counter that increments from 100 to 145 during a 5-minute interval, but only
increments during the last 3 minutes of that 5 minute interval, the metric value reported by
JMX depends on when you query JMX for the most recent value. For example:
◦
The value JMX reports for the metric at the beginning of the interval is 100.
◦
The value JMX reports for the metric at the end of the interval is 145.
◦
The value JMX reports for the metric at any time during the first 2 minutes of the interval
is 100, because, in this example, the counter does not start incrementing until the last
3 minutes of the interval.
◦
The value JMX reports for the metric at minute 4 could be any value from 100 through
145 depending on how frequently the counter value is updated by the creating application
or component between minute 2 and the end of the interval.
Metric values in memory but not persisted to disk or exposed via JMX
For metric values that are retained in memory without being persisted or exposed via JMX:
Controller components can use these values internally.
The component or application can expose this metric data in other ways, such as by including
the values in the appropriate section of a controller support report . In such cases, the values
exposed are the most recent, raw values (as would be shown if they were exposed via JMX)
instead of values for a specific time interval (such as values that are persisted to disk).

Metric identifiers

When a metric is created, it is associated with the following text strings that, taken as a
combination, uniquely identify the metric:
Application ID
(REQUIRED) Identifies the application creating the metric. For example, the application ID
for the controller is:
com.hp.sdn
metric name
(REQUIRED) Describes the metric. This name is provided by the application that creates the
metric. For example, an application that creates metrics to represent the characteristics of
traffic on device ports might use names such as:
framesTransmitted
TxFrames
framesReceived
RcvFrames
primary tag, secondary tag
Additional description of the metric, such as a category or a device. Primary and secondary
tags are optional, but if a secondary tag is provided, a primary tag must be provided. These
tags are provided by the application or component that creates the metric.
For example, an application that creates metrics to represent the characteristics of traffic on
device ports might use a primary tag to identify a device and a secondary tag to identify
specific ports on the device. The resulting metrics are structured so that for each device
(primary tag) there are multiple ports (secondary tags) that each have several metrics
associated with them.
142 Metrics