KPIOutput
The calculated KPIs and related metadata are delivered in KPIOutput
 UDRs.Â
The generation of this UDR type is triggered by the timestamp
 field of the incoming KDR
 UDRs.
When a timestamp value exceeds the upper limit of the current period by a configurable "delay", KPIAggregatedOutput
 UDRs are generated for the period, which is then considered closed. The delay is configured in the KPI agent for further information, see KPI Agent.Â
The length of a period for a KPI is defined by the window size that is set in the service model (kpi
 object). Calculated KPIs that belong to a closed period will be discarded.
The following fields are included in the KPIOutputUDRs
:
Field | Type | Description |
---|---|---|
| string | This field contains an instantiated path based on actual input data and the node path of the kpi object in the service model. Example: The |
kpi | string | This field contains the name of the kpi object in the service model. |
node | string | This field contains the node path of the For the instantiated path, corresponding to actual values in the input, see |
outputTime | long | This field contains the system time (Unix time) when the KPIOutput UDR was generated. |
outputType | int |
When a KPI is configured to generate immediate alarms, the alarm output will be generated in a |
periodEnd | long | This field contains the end time for the period, based on the incoming KDR UDR timestamps. |
| long | This field contains the start time for the period, based on the incoming |
| long | This field contains the number of KDR UDRs that were used for the KPI calculation. |
| string | This field contains the level name of threshold object in the service model. |
value | double | This field contains the result of the KPI calculation. |
windowSize | long | This field contains the length of the period. The period length is determined by |