BAC数据DEBUG(WDE & Loader Troubleshooting)

WDE

Data Collectors send data (=samples) by http requests.
Data is received by WDE which performs some processing on it: translations and validation.
Then, It publishes arrays of samples to the BUS.
When the BUS receives the samples, WDE sends acknowledges to the relevant agents 

 

 

JMX

• *Web Data Entry JMX*

 

 

log/mecury_wde:

Wde.log will contain error messages  if sample publishing fails;

WdeIgnoredSamples.log will contain received but not published samples;

WdeStatistics.log will contain statistics of receiving and publishing samples on BUS.

wdePublishedSamples.log - The samples that published

 

 

check  WDE connectivity by

http://<your_server>/ext/mod_mdrv_wrap.dll?type=test

 

this url  will return a string like :

 

Web Data Entry is up. Time is: 1259326238727

 

 

 

Loader

Loader load the data into profile DB.
The Loader is a bus subscriber that subscribes to topic that persisted samples (samples that enter to DB) from specific hos.
Provides persistency of failed insertions (Recovery connection).

 

Loader Logs (under mercury_db_loader)

• loader.log: the loader component log (if there are problems search for WARN and ERROR).
• loader.all.log: the log of the components that the loader uses.
• LoaderDeadLettersQ.log: log of the samples that arrive to dlq.
• LoaderSamples.log: prints the samples. The sample is identified by sequence id and hash code.
• LoaderStatistics.log: the statistics of the loader in resolution of overall, profile db and sample type

Configuration

• Conf file: in conf\core\Tools\log4j\mercury_db_loader\loader.properties.
  On this conf file we can determine the log level of the loader and the log level for each class.