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

Products

• CA Infrastructure Management
• CA Performance Management
• Network Observability

Issue/Introduction

Turn on logging on the DA to track the event processing

Environment

DX NetOps Performance Management, all supported versions

Cause

Support may ask you to enable event debug on the DA for troubleshooting.

Unexpected events

Missing events

No events

Resolution

copy the following file: /opt/IMDataAggregator/apache-karaf/etc/org.ops4j.pax.logging.cfg to .original

 

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

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

 

Add the following lines to the file:

#

# Alarm Logging (log4j 2.1.x format)

#

log4j2.appender.AlarmLog.type = RollingRandomAccessFile

log4j2.appender.AlarmLog.name = AlarmLog

log4j2.appender.AlarmLog.fileName = ${karaf.log}/Alarms.log

log4j2.appender.AlarmLog.filePattern = ${karaf.log}/Alarms.log.%i

log4j2.appender.AlarmLog.append = true

log4j2.appender.AlarmLog.layout.type = PatternLayout

log4j2.appender.AlarmLog.layout.pattern=%-5p | %-16.16t | %d{ISO8601} | %.32c{1} | %.32C %4L | %.24X{bundle.name} | %X{com.ca.context}      | %m%n

log4j2.appender.AlarmLog.policies.type = Policies

log4j2.appender.AlarmLog.policies.size.type = SizeBasedTriggeringPolicy

log4j2.appender.AlarmLog.policies.size.size = 100MB

log4j2.appender.AlarmLog.strategy.type = DefaultRolloverStrategy

log4j2.appender.AlarmLog.strategy.max = 10

log4j2.logger.AlarmDAOImpl.name=com.ca.im.dm.core.database.dao.impl.AlarmDAOImpl

log4j2.logger.AlarmDAOImpl.level=TRACE

log4j2.logger.AlarmDAOImpl.additivity=false

log4j2.logger.AlarmDAOImpl.appenderRef.AlarmLog.ref=AlarmLog

log4j2.logger.NormalizedDAOImpl.name=com.ca.im.dm.core.database.dao.impl.NormalizedDAOImpl

log4j2.logger.NormalizedDAOImpl.level=TRACE

log4j2.logger.NormalizedDAOImpl.additivity=false

log4j2.logger.NormalizedDAOImpl.appenderRef.AlarmLog.ref=AlarmLog

log4j2.logger.alarmimpl.name=com.ca.im.dm.core.aggregator.alarm.impl

log4j2.logger.alarmimpl.level=TRACE

log4j2.logger.alarmimpl.additivity=false

log4j2.logger.alarmimpl.appenderRef.AlarmLog.ref=AlarmLog

log4j2.logger.ThresholdScheduleTask.name=com.ca.im.dm.core.aggregator.alarm.schedule.impl.ThresholdScheduleTask

log4j2.logger.ThresholdScheduleTask.level=TRACE

log4j2.logger.ThresholdScheduleTask.additivity=false

log4j2.logger.ThresholdScheduleTask.appenderRef.AlarmLog.ref=AlarmLog

log4j2.logger.JdbcTemplate.name=org.springframework.jdbc.core.JdbcTemplate

log4j2.logger.JdbcTemplate.level=TRACE

log4j2.logger.JdbcTemplate.additivity=false

log4j2.logger.JdbcTemplate.appenderRef.AlarmLog.ref=AlarmLog

# end of Alarm Logging section

#

 

 

Save the file.

Logging is enabled immediately (file is read ‘on the fly’)

 

This debug can create huge logs, disable as soon as it is not needed!

 

To disable the logging, switch back to the .orig file

E.G.

cp org.ops4j.pax.logging.cfg org.ops4j.pax.logging.cfg.debug

cp org.ops4j.pax.logging.cfg.original org.ops4j.pax.logging.cfg

yes to overwrite.

Additional Information

Run the CA Remote Engineer to collect the files on the Data Aggregator.