Skip to Content

Working with logs

The following major log files are used by the integration with BMC TM ART. These files are stored in root/data/var/opt/victor/log.

  • tmart-Integration-web-bundle.log for information about the interaction between the Configuration page and the dashlets
  • tmart-Integration-java-bundle.log for information about the BMC TM ART Integration internal logic
  • tmart-ws-client.log for information about the connections and interaction with BMC TM ART

You can control logging settings for these log files, as described in the following tasks.

To set the log level in the tmart-integration-web-bundle.log file
  1. Locate the BMC TM ART Integration plugin in root/data/var/opt/victor/plugins and save a backup of the plugin file.
  2. Using a utility for manipulating archives (such as 7-Zip), open the plugin archive.
  3. Within the archive, navigate to the bundles\tmart-integration-web-bundle<build name and number>.war\WEB-INF\classes\logback.xml file.
  4. Open the logback.xml file, and set the logger level property to the relevant log level, as in the following line:
    <logger level="DEBUG" name="tmart-integration-web-bundle.event">
     You can choose from the following log levels (listed in descending order of detail):
    • ALL
    • TRACE
    • DEBUG
    • INFO (the default)
    • ERROR
    • OFF
  5. Save your changes in the logback.xml file and repackage it in the plugin archive file.
  6. Restart the BMC Application Performance Management Console.
To set the log level in the tmart-integration-java-bundle.log file
  1. Locate the BMC TM ART Integration plugin in root/data/var/opt/victor/plugins and save a backup of the plugin file.
  2. Using a utility for manipulating archives (such as 7-Zip), open the plugin archive.
  3. Within the archive, navigate to the bundles directory > Java bundle .jar file > logback.xml file.
  4. Open the logback.xml file, and set the logger level property to the relevant log level, as in the following line:
    <logger level="DEBUG" name="tmart-integration-java-bundle.event">
     You can choose from the following log levels (listed in descending order of detail):
    • ALL
    • TRACE
    • DEBUG
    • INFO (the default)
    • ERROR
    • OFF
  5. Save your changes in the logback.xml file and repackage it in the plugin archive file.
  6. Restart the BMC Application Performance Management Console.
To control logging in the tmart-ws-client.log file

Through the tmart-ws-client-log4j.properties file, found in root/data/var/opt/victor/conf/props, you can control various aspects of the logging in the tmart-ws-client.log file. In this properties file, you can configure the following main properties:

Objective

Property

Description and values

Log level

rootLogger

The level of detail in the log based on message severity. Messages at the level that you specify or at any more severe level are written to the log file.

You can choose from the following log levels (listed in descending order of detail):

  • ALL
  • TRACE
  • DEBUG
  • INFO (the default)
  • ERROR
  • OFF

Log file size

MaxFileSize

Maximum size of the log file, in megabytes. When this size is reached, the current log file is renamed with the addition of a numerical extension and a new log file is created.

The default is 10 megabytes.

Number of backup log files

MaxBackupIndex

Maximum number of backup log files to create before deleting the oldest.

The default is 10 log files in the log rotation cycle.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Real End User Experience Monitoring 1.2