Using debug logging in the TrueSight Infrastructure Management operator console


PATROL for Oracle Enterprise Database includes a debug logging agent action that you can enable or disable at the global or environment levels.

In the BMC TrueSight Infrastructure Management operator console, the debug logging agent action works as follows depending on if it is enabled at the Oracle database or Oracle environment level.

  • At the global level: The logging confirms that all of the PATROL for Oracle Enterprise Database environments are correctly configured.
  • At the environment level:  The logging enables debugging operations for all Oracle instances configured in this environment.

When you use an agent action, it is issued from your local console, but executed on the computer where the PATROL Agent is installed. For more information about agent actions, see  Executing agent actions on a monitor in the operator console Open link .

The information about using this agent action includes the following:

Related topics

Using

Navigating the operator console Open link

Viewing events by device in the operator console Open link

Executing agent actions on a monitor in the operator console Open link

Before you begin

You can only use an agent action when the following conditions are met:

  • You have the appropriate permissions required to execute agent actions.
  • The TrueSight Infrastructure Management Server must be a registered component with TrueSight.
  • The application class to which the monitor belongs has the menu commands defined in the KMs for PATROL Agent.
  • A restricted user must have full access to the respective CI.

To enable or disable debug logging

  1. Launch the BMC TrueSight Infrastructure Management operator console from the TrueSight console by selecting Monitoring > Devices.
  2. Select your Presentation Server device in the Device Details page and click on the action menu next to the device name.
    If you did not select the Device mapping option when you were configuring an Oracle monitoring policy, select the PATROL Agent device.
  3. Select Launch Infrastructure Management Operator console from the menu.
  4. Click Devices in the console's Navigation tree Open link and click Grid View in the console.
    View options menu
  5. From an Oracle monitor type or an Oracle environment in the device list, click the blue wrench icon in the Tools Menu and select Agent Actions > Logging.

Oracle monitor type debug agent actions

Select EnableDebug and the following agent action output confirms that debug logging has started.
Monitor type agent action output for EnableDebug

Select DisableDebug and the following agent action output confirms that debug logging has stopped.
Monitor type agent action output for DisableDebug


Oracle environment monitor type debug agent actions

Select EnableDebug and the following agent action output confirms that debug logging has started.
Environment agent action output for EnableDebug


Select DisableDebug and the following agent action output confirms that debug logging has stopped.
Environment agent action output for DisableDebug


The log files are stored in the following locations:

  • Java: PATROL_HOME/Patrol3/koekm/logs

  • PSL: PATROL_HOME/Patrol3/log/KOE-*.kmlog

The file name is based on the KM name, which is KOE for PATROL for Oracle Enterprise Database, and the Oracle database or Oracle environment name in the device list.


Was this page helpful? Yes No Submitting... Thank you

Comments