Actions

Multiple types of actions are available in boom and can be used for automation or as helper tools.

Type of Actions	Description
Remote Action	Any script or executable can be executed on a remote system where the boom Agent is installed.
Server Action	The script or executable can be started on the boom Server.
Auto Action	The Auto Action is specified in the Policy and will be automatically triggered by the boom Server. This type of action allows to resolve variables that are defined in the Policy.
Auto Action on different node	an Auto Action from an incoming Indication can be started on different boom Agent nodes.
Operator Action	This action is placed in the Policy and allows to trigger the action manually.
Internal boom Agent Action	This action gives additional information about the boom Agent.
Java Action	An action can be implemented as a Java class and can be triggered as a normal action.

Remote Actions

Usual Remote Actions are based on a script or executable located on a remote system. These actions can be used for multiple purposes. The main purpose is corrective actions and system or application tools that are able to deliver more detailed status information from the managed node. Any scripts or executables that are not available by default must be first deployed on the system by using the Binary Packages.

In the boom GUI a separate Actions View exists for the stored Remote Actions that can be used by operators and administrators as instrumentation repository.
Every action group gives as result a separate xml file on the boom Server. The boom Server does not store actions in the database. It makes easy to transfer such actions to other boom Servers. User permissions are used to restrict rights of different user groups.

Java Actions

A Java Action is an action that is implemented as a Java classes and deployed to the boom Agent system as a jar file. Usually it's part of some Binary Packages. Such classes must implement a simple com.blixx.ext.IAction java interface. Here is the syntax for using Java Actions:

IAction <full java class name> <parameters>

Automatic Actions

Automatic Actions can be explained with the following example:

The blixx MySQLDB MPI has an integrated feature that allows to catch long running queries. After such query was discovered, MPI stores the query in a temporary file and sends an Indication. The Indication matches with one of the Policy condition. The Indication object attribute of Indication reflects an monitored database instance and together with the unique id that is used in the name of the temporary file contained slow query. The "Search Text" pattern defines variables that can be extracted from incoming text. During the processing of the Policy all variables that are included in the Auto Action string will be resolved and the action becomes ready to be executed. The boom Server recognizes incoming Auto Action and triggers execution. As a result of this execution, the content of the temporary file will be stored as an annotation for the Indication.

An Operator Action works similar to the Automatic Action, except that the triggering can be initiated only by an operator and the result is shown in the action window. It can be helpful to define an Operator A that can deliver more detailed information from the remote system to the related Indication.

Default working directory for actions is $BOOM_ROOT (root installation directory of agent)