Trinity log

The topology is built on top of a TQL graph result. Trinity uses the repositories to assign a rule class to

 

a KPI, and executes the KPIs rules according to the topoplogy bottm-up manner. For each executed

 

rule Trinity delivers the current CI, KPI and a samples container. Tracking the samples handled by

 

Trinity requires turning on the DEBUG mode in:

 

\HPBAC\conf\core\Tools\log4j\mercury_online_engine\bleOnline.properties Change log level:

 

 From-

 

log4j.category.Trinity.BLE_SAMPLES=$ loglevel, trinity.samples.appender

 

To-

 

log4j.category.Trinity.BLE_SAMPLES=DEBUG, trinity.samples.appender Follow this log file:

 

\HPBAC\log\mercury_online_engine\TrinitySamples.log