Working with log files

1. On the virtual machine with the Cloud Probe, log in as root.
2. To stop the rsyslog service, run the following command:
   /etc/init.d/rsyslog stop
3. Open the /etc/rsyslog.conf configuration file.

4. To save messages to the Cloud Probe log file, probe, add the following lines to the end of the RULES section:

   # Save Probe messages to the probe log
   local5.info   /var/log/probe
5. Start the rsyslog service by running the following command:
   /etc/init.d/rsyslog start

After you set the logging level, you can rotate the log files based on age or size.

1. On the virtual machine with the Cloud Probe, log in as root.
2. In the /etc/logrotate.d directory, create a new file named probe.

3. Add the following lines for the Cloud Probe rotation rules, and modify the options. (For details, refer to Red Hat Linux documentation.)

   /var/log/probe
   {
       daily
       copytruncate
       rotate 4
       missingok
       create 0600 root root
   }

   • daily — rotates the log file every day
   • copytruncate — creates a copy of the original log file and truncates the original file (probe)
   • rotate 4 — limits the number of log file rotations, creating backup files
   • missingok — continues without an error message if the the log file is missing
   • create 0600 root root — (optional) creates a copy of the original log file, with specified permissions and groups
4. (Optional) You can check (debug) the rotation settings by running the following command:
   logrotate -d /etc/logrotate.conf
    The command tests the settings without actually rotating files.

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.

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.

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: