KPI Agent(4.1)
The KPI agent sends incoming KPI calculations based on the data in the incoming KDR
UDRs and the Service Model of the selected KPI profile. The agent routes the output to the workflow as KPIAggregatedOutput
UDRs.
Configuration
Setting | Description |
---|---|
KPI Profile | Click Browse to select a predefined KPI profile. The profile contains the service model configuration. |
Delay | The delay setting specifies a period that is added to the upper limit of each KPI output period. If the timestamp of a |
Input/Output Data
The Input/Output data is the type of data an agent expects and delivers.
The KPI Cluster In agent expects KDR
 UDRs and delivers KPIAggregatedOutput
 UDRs.
MIM
For information about the MIM and a list of the general MIM parameters, see Administration and Management(3.3).
PublishesÂ
MIM Parameter | Description |
---|---|
Error Counter | This MIM parameter contains the number of errors that have occurred since the workflow was started.
|
Discarded KPIs | This MIM parameter contains the number of calculated KPIs that were discarded since they belong to a previously closed period.
|
Model Config | This MIM parameter contains the name of the KPI Profile in the agent configuration.
|
Model Version | This MIM parameter contains the version of the KPI Profile in the agent configuration.
|
Accesses
This agent does not access any MIM parameters.
Agent Message Events
There are no message events for these agents.Â
Debug Events
Debug messages are dispatched in debug mode. During execution, the messages are displayed in the Workflow Monitor.
Example - Debug events
Failed to match dimension:
At least one node is missing in /tree1/AMERICAS/country/Country.AvgSales forÂ
input Map(region -> AMERICAS, amount -> 563.75, xcountry -> Mexico)
Failed metric calculation:
Failed to evaluate KPI(Region.AvgSales), EXPR(Some(Expr(amount)))Â
INPUT: Map(xamount -> 505.0)
Â
You can configure Event Notifications that are triggered when a debug message is dispatched. For further information about the debug event type, see Debug Event(3.3).
Â