Online Helps > Rule Execution Server Console > Monitoring Transparent Decision Services

Using the Rule Execution Server Console, transparent decision services can be monitored in the form of receiving statistics on an executed ruleset path.

To view statistics on a transparent decision service:

  1. Click the Explorer tab.
  2. Click Decision Services in the Navigator panel to display the Transparent Decision Services View.
  3. You can limit the displayed transparent decision services using the Display by: 5, 10, 50, 100 filter.
  4. Click the name of the relevant transparent decision service in the Transparent Decision Services View.
  5. The Transparent Decision Service View is displayed. You now have a full description of the transparent decision service including: name, ruleset path, enabled/disabled, properties, and the instances.
    You can limit the displayed instances using the Display by: 5, 10, 50, 100 filters.
    If a transparent decision service instance has been executed, a statistics link appears in the instances table in the executed ruleset path row.
  6. Click View Statistics to open the Transparent Decision Service Statistics View.

The statistics are calculated from data passed to IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration) and IlrDecisionServiceMBeanManager.addError(long timestamp).

If the executedRulesetPath changes during the life of the MBean, the statistics are automatically erased.

Transparent decision service statistics are not saved so when the service is unregistered, the statistics are lost.

The following statistics are reported:

Decision Service Statistics
Metric 
Description 
Errors Count 
This is the number of times the transparent decision service execution has failed (cf IlrDecisionServiceMBeanManager.addError(long timestamp)). 
Error Last Date 
This is the date of the last transparent decision service execution failure (cf IlrDecisionServiceMBeanManager.addError(long timestamp)). 
Count 
This is the number of times the transparent decision service has been successfully executed (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
Total Time (ms) 
This is the total time taken to execute the transparent decision service (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
Average Time (ms) 
This is the average time taken to execute the transparent decision service (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). It is derived from the total execution time (Total time (ms)) and the number of executions performed (Count). 
Min. Time (ms)  
These are the shortest transparent decision service execution times (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
Max. Time (ms) 
These are the longest transparent decision service execution times (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
Last Execution Time (ms) 
This is the time of the last transparent decision service execution (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
First Execution Date 
This is the date of the first transparent decision service execution (cf iIlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 
Last Execution Date 
This is the date of the last transparent decision service execution (cf IlrDecisionServiceMBeanManager.addMeasurement(String executedCanonicalRulesetPath, long timestamp, long duration)). 

See Also

Viewing and Managing Transparent Decision Services | Monitoring and Managing the Server | Editing a Transparent Decision Service | Changing the Status of a Transparent Decision Service