The following scheme demonstrates a KPI Management provisioning and processing scenario.

Provisioning and processing

A user provisions a service model configuration directly via a REST interface or via a KPI profile in the Desktop.
Hint!

Existing profiles and service models can be viewed in the Web UI as well.
The user then submits a configurable application to the Spark cluster, which performs the KPI calculations.
Input data is received by the KPI Cluster In agent via KDR UDRs. The agent encapsulates these UDRs in KafkaUDRs that are then sent to a dedicated input topic via a Kafka Producer agent.
The Spark cluster periodically polls the input topic and performs the KPI calculations that are based on the service model and the input data. The polling interval depends on the duration of the Spark batch intervals.
When the timestamps of the input data indicate that a configurable time period has elapsed, the Spark cluster sends the calculated KPIs to a dedicated output topic. There is also a separate topic for alarm output. If the service model has been configured to produce immediate alarms, the Spark cluster sends the KPIs that hit an alarm level, within a Spark batch, potentially before their KPI period closes.
The data on the output and alarm topics are collected via Kafka Collector agents. The KPI Cluster Out agent extracts and decodes the KPI data to KPIAggregatedOutput UDRs.

This chapter includes the following sections:

Browser not supported