
The Web Component Framework 59
Core Concepts
first history object should be no greater than the start time of the time range, and the end
time of the last history object should be no less than the end time of the time range.
When there are multiple metrics calculated for the same non-RAW time range (whether
they are different metrics on the same object, or the same metric on different objects),
they must have exactly the same number of history objects as each other, and the start
times and end times of the history objects at the same indices in their lists must be
identical.
If there are no agent observations that correspond to a history object within a certain
granularity interval in a non-RAW time range, a history object is still created, with the
appropriate start time and end time, but none of the value properties are filled in.
Metric Observations
An observation of a numerical value is called a metric.
Data collected by agents is generally expected to be collected into a Metric data object.
Certain components, such as the chart components, must be bound to Metric objects to
function.
Metric definitions must specify the unit property in the Metric’s containing Property
class. The unit is used to display numeric data. In particular, the unit’s precision
property is used by some components (such as charts) and renderers to ensure the
correct number of decimal places are used when rendering data. If the Metric’s precision
is desired to be different than its unit’s precision, you can set the precision directly on
the Metric’s containing Property class using the precision property.
Metrics must conform to the following schema:
Metric
Property Type Description
uniqueId String unique ID
name String name of metric, localizable
period MetricValue value for entire time range
current MetricValue value for last interval in time range
history MetricValue;
is-many = true
list of values for each interval in time range
Comentarios a estos manuales