CA SOI captures various KPIs that enable you to pinpoint performance problems for specific event processing modules. You can use these KPIs to verify that all processing modules are operating correctly and efficiently. This information assists you in performing detailed diagnostics to assess the health of each module. Proper analysis of this information can further help you quickly identify and resolve associated issues. For example, the KPIs data can provide more performance-related information about why your environment is running slow, and can help you take appropriate measures.
The KPIs are written to individual connector-specific XML files, which are named as mdrprod-mdrprodinstance.xml (for example, CA-09998-LOD20.abc.com.xml, CA-09997-LOD20.abc.com.xml, and CA-09993-LOD20.abc.com.xml). Each connector-specific KPIs file is stored in the SOI_HOME\resources\Core\Kpi folder. These KPIs are collected for the type Core, which includes all core event processing modules (for example, Classifier and Evaluator). The following list describes all of the assessed KPIs:
Specifies the time that the module has been processing events in milliseconds.
Specifies the total number of events that processed since the module was last started.
Specifies the most recent event throughput value in events per second.
Specifies the average event throughput in events per second since the module was last started.
Specifies the maximum event throughput in events per second since the module was last started.
Specifies the minimum event throughput in events per second since the module was last started.
Specifies the number of events that have been filtered since the module was last started. This KPI covers events that are filtered explicitly according to the Filter operation in the policy and implicitly because of their inability to be classified.
Specifies the number of events queued for a given module to process since the module was last started. Longer queues indicate a backlog of events. A status of Warning indicates more than 300 queued events, and a status of Critical indicates more than 500 queued events.
Specifies the number of code exceptions since the core was last started.
Specifies the number of active processing threads since the core was last started. Additional threads are created for performing normalization and enrichments. A status of Warning indicates more than 100 active threads, and a status of Critical indicates more than 200 active threads.
Specifies the total number of times a fully qualified domain name was successfully resolved and added to the internal cache since the core was last started.
Note: These names expire from the cache every 120 seconds by default.
Specifies the total number of times a fully qualified domain name was unable to be resolved since the core was last started.
Note: The name null is placed in the cache when this scenario occurs. These names expire from the cache every 120 seconds by default.
(Evaluator only) Specifies the total number of Drools rules that are activated on an event since the module was last started.
(Evaluator only) Specifies the total number and type of Drools rules that are activated on an event for a specific policy since the module was last started. For example, a line <kpi name='ABC-EnrichEvent' value='3' status='NORMAL' /> in a KPIs file specifies that the rule of type EnrichEvent was triggered three times for a policy with the name ABC.
|
Copyright © 2013 CA.
All rights reserved.
|
|