Product Log Files

OpsCx for VROPS 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

The log files and their locations in consolidated setups are different from the ones in distributed setups.

Consolidated Setups

OpsCx for VROPS creates and maintains log files in the <OvDataDir>/log directory. The log file names contain the log file creation date. There is one log file for each integrated VROPS data type: vropsevents.<Date>.log, vropstopology.<Date>.log, vropsmetrics.<Date>.log.

In a consolidated setup, to change location of the log file for an integrated VROPS entity type, perform these steps:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntVROps and open the appropriate integration configuration file (vrops_event.conf, vrops_topology.conf, or vrops_metrics.conf) 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.

Distributed Setups

OpsCx for VROPS creates and maintains a log file vropsremote.<Date>.log on both systems where the product is installed. The log file locations are as follows:

• On the Operations Connector host: The <OvDataDir>/log directory

To change location of the log file on a particular system, complete the following procedure:

1. Considering the role of the system where the log file resides, change the current directory to:

   • Operations Connector host: <OvDataDir>/conf/HPBsmIntVROps

2. Open the appropriate shared integration configuration file (bsmc_remote.conf or
   vrops_remote.conf) in a plain text editor.

3. In the genintd section, change the value of the log-file option.

4. Save your changes.

5. Restart the shared integration service as described in Restarting the Services topic.

Logging Severity Levels

Log entries have different severity levels. InOpsCx for VROPS, 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 (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 VROPS aspect or for a system in a distributed setup, perform these steps:

1. Change the current directory as described in Log Files Location topic.

2. Open one of the integration configuration files (vrops_event.conf, vrops_topology.conf, vrops_metrics.conf, bsmc_remote.conf, or vrops_remote.conf) in a plain text editor.

3. In the genintd section, perform the following:

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

   2. In the same line, replace the value 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"

4. Save your changes.

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

Related topics

Restarting the Services

Log Files Location