Product Log Files

Ops Connector for OEM records actions performed by its event and topology integration services into log files. Occurrences of unexpected behavior are also added as entries into the log files. You can use the logged information to investigate issues.

For more information about metric log data, make sure to enable opcgeni trace for debugging.

Log Files Location

Ops Connector for OEM creates and maintains log files in the <OvDataDir>/log directory. There is one log file per day for integrated OEM event entity type. For Topology, the log file will be rolled over based on its size. The maximum size limit is 10MB per file, and it can hold up to 10 files at any point of time. The log file names for each integrated OEM entity types (events and topology) as follows:

oem_events.<Date>.log, oem_topology.log.

To change location of the log file for a particular integrated OEM entity type, perform these steps:

For Events:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntOEM/genint and open oem_events.conf in a plain text editor.

2. In the genintd section of oem_events.conf file, change the value of the log-file option. Preserve the %d placeholder in the log file name.

3. Save your changes.

4. Restart the event integration service as described in Restarting the Services topic.

For Topology:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntOEM/classpath and open the application-defaults.properties file in a plain text editor.

2. Change the value of topology.output.file option.

3. Save your changes.
4. Restart the topology integration service as described in Restarting the Services topic.

Logging Severity Levels

Log entries have different severity levels. In Ops Connector for OEM, the following levels are available for event integration:

Severity Level	Keyword	Meaning
0	No Log	logging is disabled
1	Error, Config	errors, current values of integration configuration options
2	Info, Warning	information messages, warnings
3	Trace	tracing (debugging) messages

By default, the logging severity level is set to 1 (internal default), which means only errors and configuration-related messages are logged. For troubleshooting purposes, you can change the level.

When a particular logging level is set, it causes messages with lower severity level to be recorded as well. For example, if the severity level is set to 2, information messages, warnings, errors, and configuration-related messages are logged, but tracing messages are not.

To change the logging severity level for an integrated OEM entity type, perform these steps:

For Events:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntOEM/genint and open the oem_events.conf file in a plain text editor.

2. In the genintd section, perform the following:

   1. Uncomment the line with the log-level option.

   2. In the same line, replace the value placeholder in quotation marks with the chosen logging severity level.

   For example, to change the logging severity level from the default level to 2, change the line

   //, "log-level" : "3"

   to

   , "log-level" : "2"

3. Save your changes.

4. Restart the event integration service as described in Restarting the Services topic.

For Topology:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntOEM/classpath and open the application-logging.properties file in a plain text editor.

2. To enable trace for topology integration, change the value of logging.level.com.hp option to TRACE.

3. Save your changes.
4. Restart the topology integration service as described in Restarting the Services topic.

Related Topic

Restarting the Integrations