Page tree
Skip to end of metadata
Go to start of metadata

To help diagnose problems in PATROL for Application Management, you can enable debug trace files to help identify problems.

These trace files are also useful to have before contacting BMC Customer Support. The files contain information that Customer Support can use to quickly identify the problem that is preventing normal operation.

The debug commands are entered in the Command box accessed through the Infrastructure Management Operations Console .

Debug commands

The PATROL Agent debug enable and disable commands are as follows:

Enable commandDisable commandDescription
set("/APM_MAIN/APM/_CentralAdminCollector/paramDebug", "1,3,FILE");unset("/APM_MAIN/APM/_CentralAdminCollector/paramDebug");

The command uses the _CentralAdminCollector parameter to create a trace file that contains data from the collector.

Use this command when:

  • An application management configuration from Central Monitoring Administration is loaded in the PATROL Agent, and the Synthetic branch does not exist under the AM branch.
  • The application management knowledge module configuration is not recognized.
  • Changes to the AM knowledge module configuration in CMA does not take effect.
set("/APM_MAIN/APM/_AppVisibilityDiscovery/paramDebug", "1,3,FILE");unset("/APM_MAIN/APM/_AppVisibilityDiscovery/paramDebug");

Use this command if the _AppVisibilityDiscovery parameter fails.

The command looks for App Visibility portal data in the TrueSight Presentation Server, and creates a trace file that contains the data.

set("/APM_Synthetic/APMSynthetic/_Discovery/paramDebug", "1,3,FILE");unset("/APM_Synthetic/APMSynthetic/_Discovery/paramDebug");

Use this command if the _Discovery parameter failed to:

  • Access the latest configuration from the App Visibility portal.
  • Failed to delete old instances in the tree. 

The command creates a trace file that contains the Synthetic hierarchy in the Presentation Server.

set("/APM_Synthetic/APMSynthetic/_DataCollector/paramDebug", "1,3,FILE");unset("/APM_Synthetic/APMSynthetic/_DataCollector/paramDebug");

Use this command if the _DataCollector parameter failed, or the wrong Synthetic data instances were created in the application management knowledge module.

The command creates a trace file that collects the information about TrueSight synthetic monitoring with Silk Performer when the _DataCollector parameter failed.

Running the PATROL for Application Management debug commands

  1. Perform one of the following tasks:
    • In the Main drawer, select Global > Devices click the grid view icon , and then click the blue wrench icon for the device on which you want to run the debug command.
    • Double-click a device name to display the Show Monitors page, and then click the blue wrench icon for the agent on which you want to run the debug command.
  2. Select Query Agent.
  3. Enter a debug command in the Command box and press Enter, or click Execute. The result is displayed in the Command box. You can run additional debug commands by entering the command into the Command box.

The trace file that collects the data is saved on the PATROL Agent host machine as:

%PATROL_HOME%/APM_KM/APMdebugParamFileName-APM.trc

To disable a debug command, enter the disable command in the Command box.

 

Notes

  • Restarting the PATROL Agent disables all of the debug commands. Debug information is not collected on the restarted PATROL Agent.
  • Because the debug file consumes large amounts of disk space, do not to let the debug commands operate for longer than two hours.
  • Delete the debug trace file from the PATROL Agent host machine after it is no longer needed. Debug files create a new entry each time a debug command is entered, and many debug commands cause the debug file to consume a large amount of disk space.
  • When you send a trace file to Customer support, also send the following application management log files:
    • APM_PSL_<MonthDayYearHourMinuteSecond>.log (for example: APM_PSL_ 102115125634.log)
    • JDCollector.log (for example: JDCollector.log1, JDCollector.log2 )

1 Comment

  1. hi,

    can you please add the following to the documentation (also for earlier versions like 10.1)

     

    Please note : In some case the trace file (after enabling debug) is not generated under %PATROL_HOME%/APM_KM/ if you encounter this situation look for the trace file under %PATROL_HOME%/profile and open the folder named with the patrol agent process owner e.g %PATROL_HOME%/profile/patrol

    don't forget to unset the debug trace after sending me the logs

    thanks