Agent actions

When you execute an agent action, it is issued from your local console, but executed on the computer where the PATROL Agent is installed. Agent actions are also called menu commands in BMC PATROL and vary from KM to KM. All Knowledge Module (KM) menu commands are not exposed in BMC ProactiveNet and TrueSight consoles. 

Note

 You can execute agent actions on monitors that are configured using BMC PATROL Agent version 9.6 or later.

The Agent Actions option is available only when the following conditions are met:

  • You have appropriate permissions required to execute agent actions. 
  • The application class to which the monitor belongs has the menu commands defined in the KMs for BMC PATROL Agent.

Permissions required to execute agent actions

You must have the Allow execution of Agent Action permission assigned to have the Agent Actions option in the Tools menu. If you do not have the permission assigned, the Agent Actions option is not displayed in the Tools menu.

By default, the following roles have the Allow execution of Agent Action permission:

  • Super Admin
  • Event Administrator
  • Data Collection Administrator
  • Service Administrator

For other roles, these permissions must be assigned by the administrators to access the agent actions.

Main agent actions available in PATROL for IBM DB2

The supported agent action for BMC PATROL for IBM DB2 is as follows:

  • Logging - It enables the main PSL logging. The file is located under: Patrol3/log/PSO_<DB type>_main-<Agent host>-<Agent port>.kmlog

Environment agent actions available in PATROL for IBM DB2

The supported agent actions for BMC PATROL for IBM DB2 are as follows:

  • Force discovery - It forces to discover all the components of the environment hierarchy.
  • Diagnostic report - It creates a diagnostic report of the environment. The output will be saved in a xml file at <Patrol Home>/Patrol3/pso/report/diag/<<environment name>>_DiagnosticReport.xml.
  • Restart monitoring - It restarts the monitoring of the environment. It stops the external backend processes and destroys the environment monitoring instance from console. It creates the environment instance again and starts the external backend collector of the instance to start the monitoring from the beginning.
  • Logging - It enables debugging operations for configured environment. This enables the PSL and Java logging of the specified environment.

    The PSL debug file of the environment is located under:

    Patrol3/log/PSO_<DB type>^<environment name>-<Agent host>-<Agent port>.kmlog

    The Java debug file of the environment is located under:

    Patrol3/pso/logs/java/<DB type>^<environment>_<Agent port>_JavaCollector.log

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

Comments