We are seeing alarm differences between NetOPs and DX02 products. How can we enable debug to troubleshoot this further?
Spectrum Data Publisher. (SPUB). (OI Connector)
Release : ANY
Debug logs to further troubleshoot the problem
To enable debug on SPUB Connector please enable the following
1. From /SpectrumDataPublisher/config folder, please make a backup of the log4j2.properties file and then edit as follows, under SpectrumDataPublisher.log section change the 2nd to the last line to fatal as shown below
appender.commonlog.type = RollingFile
appender.commonlog.name = CommonLog
appender.commonlog.fileName=${logdir}/SpectrumDataPublisher.log
appender.commonlog.filePattern=${logdir}/SpectrumDataPublisher_${filePattern}
appender.commonlog.layout.type = PatternLayout
appender.commonlog.layout.pattern = ${pattern}
appender.commonlog.policies.type = Policies
appender.commonlog.policies.size.type = SizeBasedTriggeringPolicy
appender.commonlog.policies.size.size = 100MB
appender.commonlog.strategy.type = DefaultRolloverStrategy
appender.commonlog.filter.threshold.type = LevelRangeFilter
appender.commonlog.filter.threshold.minLevel = fatal
appender.commonlog.filter.threshold.maxLevel = trace
2. Near the very bottom of the log4j2.properties file you will see the following and change from false to true
logger.alarmLogger.name=ALARM_LOGGER
logger.alarmLogger.additivity = true
logger.alarmLogger.appenderRef.alarmlog.ref = AlarmLog
3. Change the logger.alarmLogger.level from info to trace.
# set the log level to trace to store payloads of the sync data.
logger.alarmLogger.level = trace
3. Save the log4j2.properties file and then stop and start the connector from /SpectrumDataPublisher from the command line so that the debug changes will take affect.
For Linux Connector
./run.sh stop
then
./run.sh start.
For Windows Connector
from command line
run.bat stop
then
run.bat start
The logs will be output to /SpectrumDataPublisher/logs as SpectrumDataPublisher.log and Alarm.log files.
The logs will automatically roll over and be dated