Product Log Files

OpsCx for Microsoft SCOM records actions performed by its event, topology, and metric 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.

Log Files Location

OpsCx for Microsoft SCOM creates and maintains log files in the <OvDataDir>\log directory. There is one log file for each integrated Microsoft SCOM aspect (events, topology, and metrics) of each integrated Microsoft SCOM instance. The log file names contain the version of the Microsoft SCOM instance from which data is collected, the data type indicator, and the log file creation date. For the second and each additional integrated Microsoft SCOM instance, the consecutive number of the instance is added to the filenames. For example:

• The name of the log file of the event integration with the first (only) Microsoft SCOM instance, whose version is 2007, is scom2007e.<Date>.log.

• The name of the log file of the topology integration with the second Microsoft SCOM instance, whose version is 2012, is scom2012t2.<Date>.log.

To change location of the log file for an integrated Microsoft SCOM entity type, perform these steps:

1. Change the current directory to <OvDataDir>\conf\HPBsmIntSCOM\genint and open the appropriate integration configuration file in a plain text editor.

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

3. Save your changes.

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

Logging Severity Levels

Log entries have different severity levels. In OpsCx for Microsoft SCOM, the following levels are available:

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, 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 Microsoft SCOM entity type, perform these steps:

1. Change the current directory to <OvDataDir>\conf\HPBsmIntSCOM\genint and open the appropriate integration configuration 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 affected integration service.

Related topics

Restarting the Services