ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to Enable the DA (Data Aggregator) Events/alarms in Debug mode

book

Article ID: 142308

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

How to Enable the DA (Data Aggregator) Events/alarms in Debug mode

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Resolution

Steps to enable the alarm debug on DA to collect all logs after 2-3 poll cycles, but we shouldn't keep it on for a long time.

Turn on logging on the DA to track the alarm processing:

1 - Edit the following file: /opt/IMDataAggregator/apache-karaf-2.4.3/etc/org.ops4j.pax.logging.cfg 

The path may differ depending on where the DA is installed. 

2 - Add the following lines to the file:

log4j.category.com.ca.im.dm.core.aggregator.alarm.impl=TRACE,sift
log4j.category.com.ca.im.dm.core.database.dao.impl=TRACE,sift
log4j.additivity.com.ca.im.dm.core.aggregator.alarm.impl=false
log4j.additivity.com.ca.im.dm.core.database.dao.impl=false

3 - Once you have captured the debugging output required, turn off the logging entries by commenting them out with a "#" prefix at the beginning of each configuration file entry added. 


4 - Then, save the file to disable the logging immediately. 

NOTES: o TRACE level logging can generate a significant amount of log entries and slow processing down, so, only keep TRACE level logging on for the shortest period of time possible needed to debug

Finally collect the RemoteEngineer logs from DA:

<install_home>/RemoteEngineer/re.sh

Powered by Wolken Software