Using Traces

The trace function enables you to store a history of actions performed by PATROL KM for Exchange Servers in various areas for remote monitoring.

The trace function enables you to keep track of the processing of data received by PATROL KM for Exchange Servers, and serves as an important tool in troubleshooting problems in the KM.

To set up a BMCCmdlet trace

The BMCCmdlet trace function enables you to store a history of data collection actions performed by the External BMCCmdlet Process Settings for a remote Exchange Server. 
This function is only applicable for the Remote Exchange application class.

1. Access the Remote Exchange application class as described in the  Accessing KM Menu Commands.
2. Select Trace menu > Setup trace for BMCCmdlet external process to display the BMCCmdlet trace dialog box.
3. Select the check box to turn on the trace for the external BMCCmdlet process settings.
4. Click OK.

To set up a discovery trace

The Discovery Trace function enables you to store a history of all actions pertaining to application class discovery and proper hierarchical organization of data for remote Exchange Servers.

1. Access the relevant application class as described in the  Accessing KM Menu Commands.
2. Select Trace menu > Setup trace for Discovery to display the Configure Trace Options Application Classes dialog box. The relevant application class appears in the fiels on the left.

3. Set trace level to a level higher than 0 to activate the trace. Choose from the following values. The higher the trace level, the more detailed the stored history:
   
   

   Trace Level	Description
   0	Trace off
   1	Basic milestones only, especially messages notifying of the beginning and the completion of actions invoked by menu commands
   2	Detailed information, including functions that were called
   3	More detailed information, including arguments (this level does not appear for all application classes)

4. In the Output destination field, select either Window for display of the trace through the PATROL Console desktop, or File for storing the trace as a file in the %patrol_home%\profile\<agent user> directory.
5. Click Apply and then click Close.

To set up a menu command trace

The Trace function for menu commands enables you to store a history of all actions invoked through the menu commands associated with an application class belonging to a remote Exchange Server.

1. Access the relevant application class as described in the  Accessing KM Menu Commands.
2. Select Trace menu > Setup trace for Menu commands to display the Configure Trace Options Menu Commands.
3. Select the trace instance in the field on the left.

4. Set trace level to a level higher than 0 to activate the trace. Choose from the following values. The higher the trace level, the more detailed the stored history:

   Trace Level	Description
   0	Trace off
   1	Basic milestones only, especially messages notifying of the beginning and the completion of actions invoked by menu commands
   2	Detailed information, including functions that were called
   3	More detailed information, including arguments (this level does not appear for all application classes)

5. In the Output destination field, select either Window for display of the trace through the PATROL Console desktop, or File for storing the trace as a file in the %patrol_home%\profile\<agent user> directory.
6. Click Apply and then click Close.

To set up a parameter trace

The Parameter Trace function enables you to store a history of data collection actions performed by the standard parameters within certain application classes belonging to a remote Exchange Server.

1. Access the relevant application class as described in the  Accessing KM Menu Commands.
2. Select Trace menu > Setup trace for Parameter to display the Configure Parameter Trace Options dialog box.

3. Select the parameter in the field on the left.

   Note

    Although all parameters in the application class are listed, parameter traces are currently available only for the collector/standard parameter in each application class.

4. Set trace level to a level higher than 0 to activate the trace. Choose from the following values. The higher the trace level, the more detailed the stored history:

   Trace Level	Description
   0	Trace off
   1	Basic milestones only, especially messages notifying of the beginning and the completion of actions invoked by menu commands
   2	Detailed information, including functions that were called
   3	More detailed information, including arguments (this level does not appear for all application classes)

5. In the Output destination field, select either Window for display of the trace through the PATROL Console desktop, or File for storing the trace as a file in the %patrol_home%\profile\<agent user> directory.
6. Click Apply and then click Close.