Matcher log

Trinity listens to BAC's BUS and delivers every sample to the Matcher.

The Matcher uses the CIs/KPIs selectors to determine which element accepts that sample.

 

Tracking the samples handled by Matcher requires turning on the DEBUG mode in:

<Processing machine>\HPBAC\conf\core\Tools\log4j\mercury_online_engine\bleOnline.properties

Change-

#log4j.category.Trinity.com.mercury.am.platform.processing.ble.core.impl.matcher=$loglevel, trinity.file.appender

To-

log4j.category.Trinity.com.mercury.am.platform.processing.ble.core.impl.matcher=DEBUG, trinity.file.appender

 

In order to realize what sample in mapped to a sample number turn on the TrinitySample DEBUG mode in the same file

Change-

log4j.category.Trinity.com.mercury.am.platform.processing.ble.core.impl.matcher=$loglevel, trinity.file.appender

To-

log4j.category.Trinity.com.mercury.am.platform.processing.ble.core.impl.matcher=DEBUG, trinity.file.appender
 

Follow this log file:

<Processing machine>\HPBAC\log\mercury_online_engine\Trinity.log

and

<Processing machine>\HPBAC\log\mercury_online_engine\TrinitySamples.log
Note: Do not forget to turn off the DEBUG mode when done; The Matcher log appender in commented in default.

 

 

 

Problem

Monitor KPI is not calculating

Solution

Check for matching samples in TrinitySamples.log on MercuryAM\log\mercury_online_engine :
In bleOnline.properties file on MercuryAM\conf\core\Tools\log4j\mercury_online_engine
1. Change BLE_SAMPLES to debug
2. Add this line to the properties file
log4j.category.Trinity.com.mercury.am.platform.processing.ble.core.impl.matcher.BLEContextMatcherImpl=DEBUG, trinity.samples.appender

a. In case you find your sample and there is a match-

Context DASHBOARD for 1 received sample (#6867):
...sample details...
For sample #6867 of type trans_t in context DASHBOARD for 1 the matching is [59c6a274e0a8761eb89bff7bfd3df0d0]

There could be a problem with the timestamp, check if the BAC machine time is synchronize with the DB machine time.

b. In case you find your sample and there is no match-

Context DASHBOARD for 1 received sample (#7203):
...sample details...
No match for sample #7203 of type event in context DASHBOARD for 1

There could be a problem with the selector, check for the selector definition on Dashboard Admin.

c. In case the sample is not in the file, although you have send it, then look at dispatcher_log.txt on MerucyrAM\log\core there you can see the samples as they were received from the BUS- and the error that prevents them from getting to TrinitySamples.log and to the DB.

d. If none of those solutions work - look at bam.app.rules.log, rulesfwk.log and Trinity.log for errors.

<!-- <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"> <rdf:Description rdf:about="http://rndwiki.atlanta.hp.com/confluence/display/cord/Matcher" dc:identifier="http://rndwiki.atlanta.hp.com/confluence/display/cord/Matcher" dc:title="Matcher" trackback:ping="http://rndwiki.atlanta.hp.com/confluence/rpc/trackback/200730" /> </rdf:RDF> -->