How to enable the OneView monitor log

Article Id: 103156
Status: Published
Updated On: 22-06-2018 12:58
Products:
CA Single Sign On Secure Proxy Server (SiteMinder) , AXIOMATICS POLICY SERVER , CA Single Sign On SOA Security Manager (SiteMinder) , CA Single Sign-On , CA Single Sign-On
Issue/Introduction:

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, Common Settings, API Logging Levels, and 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

Environment:

Release:
Component: SMPLC

Resolution:

Here is what the trace.conf looks like when you enable all trace events to be written out to a log file, monitor.log

# Common logging settings
nete.enableConsoleLog=0
nete.enableFileLog=1
nete.logFile=C:\\Program Files\\CA\\siteminder\\config\\monitor.log 

# 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=2
nete.conapi.ipc.logLevel=2
nete.conapi.tcpip.logLevel=2

# Monitoring infrastructure modules logging settings
nete.mon.agentLogLevel=2
nete.mon.monitorLogLevel=2
nete.mon.monitorDbLogLevel=2
nete.mon.monitorChannelLogLevel=2
nete.mon.monitorChannelTrLogLevel=2
nete.mon.monitoringApiLogLevel=2
nete.mon.monitorClientApiLogLevel=2
nete.mon.monitoringAgentProxyLogLevel=2
 

Additional Information:

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