Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Triggering remote actions


You can trigger remote actions in any of the following ways:

  • Using the Event Rule Wizard: On receiving an event, matching event rules are identified. If the matching event rule has a remote action assigned, the remote action is run. An event rule can be defined through the operator console. For more information about adding an event rule, see Adding-a-basic-event-rule-type
  • Using remote action policies: To set up automatic remote actions that are triggered by events, you must first define a remote action policy using the administration console. The policy contains the definition of the event that triggers it. When the specified event is received, it triggers the rule, which invokes the remote action. For more information, see Defining-a-remote-action-policy
  • Using the event list: You can also trigger a remote action from the event list of the operator console. You can also select and run any of the pre-defined commands. For more information, see Executing-remote-actions.  
  • Using the All Devices Grid View in the operator console: If a remote action is defined for an associated device of a particular operating system and monitor types, the remote action is listed under the Tools option for the device and instance of the monitor type in the Operations Console.

Related topic

Defining-a-remote-action-policy

 

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