Setting debugging options


Debug saves all messages from the PATROL KM and the external processes that connect to Force.com. This information can be useful for troubleshooting your installation or configuration.

To set general debugging options by using menu-commands

  1. Right-click the XXXXX (icon and select KM Commands > Set Debug Log Level.
     The Debug dialog box displays the following options.
    • Collector Debug: Select one or more following options if you want debugging information for the collector parameters.
      • Finest: Activates debugging and provides the most detailed information about the collector parameters.
      • Finer: Activates debugging and provides more information about the collector parameters.
      • Info: Activates debugging and provides information only about informational messages generated for the collector parameters.
      • Warning: Activates debugging and provides information only about potentially harmful events for the collector parameters.
      • Severe: Activates debugging and provides information only about the critical error events for the collector parameters.
  2. Click Accept.
     The settings are applied. When the account is discovered or configured, debugging messages appear in a task output window.
  3. Click Close.

The debugging output is redirected to the System Output Window (SOW). Collector debugging generates a log file in the Patrol3/log directory. Separate log files are created for the KM, and each Force.com account:

  • The log file for the Force.com KM is named as FRC_PSL_MMDDYYHHMMSS.log, where MMDDYY is the date, and HHMMSS is the time.
  • The log file for individual Force.com accounts is named as XXX_AccountName.log.0, where AccountName is the name of the Force.com account.

 

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

BMC PATROL for BMC Server Automation 8.2