Sometimes, it may be necessary to enable logging of the OneView Monitor for troubleshooting. But the manual configuration is not necessarily clear so it may not work properly.
The default trace.conf is broken into 3 sections:
1. Common Settings
2. API Logging Levels
3. Infrastructure modules logging.
# There are three levels:
# 0 - no trace events
# 1 - error and warning trace events
# 2 - all trace events
# Common logging settings
nete.enableConsoleLog=0
nete.enableFileLog=0
nete.logFile=
# Connection API logging levels. There are three levels: 0 - no trace events, 1 - error and warning trace events,
# 2 - all trace events
nete.conapi.logLevel=1
nete.conapi.ipc.logLevel=1
nete.conapi.tcpip.logLevel=1
# Monitoring infrastructure modules logging settings
nete.mon.agentLogLevel=1
nete.mon.monitorLogLevel=1
nete.mon.monitorDbLogLevel=1
nete.mon.monitorChannelLogLevel=1
nete.mon.monitorChannelTrLogLevel=1
nete.mon.monitoringApiLogLevel=1
nete.mon.monitorClientApiLogLevel=1
nete.mon.monitoringAgentProxyLogLevel=1
Release: 12.8.x
Component: SMPLC
Note that the Common Logging settings for
nete.enableConsoleLog=0
nete.enableFileLog=0
are either 0 or 1. The 0 is for disable and the 1 for enable. For the other settings, 0,1, and 2 are used to indicate the tracing level.
# There are three levels:
# 0 - no trace events
# 1 - error and warning trace events
# 2 - all trace events
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/symantec-security-software/identity-security/siteminder/12-8/installing/install-oneview-monitor.html