Monitoring overview


boom knows two types of policies:

 Indication Policy: This type of policy is used for all text related processing.

 Monitor Policy: This type of policy is used for threshold monitoring.

boom policy types

Indication policy subclasses and types

The indication policy itself is divided into two subclasses:

Indication policy: A simple indication policy is used for processing incoming messages. No trigger (no Nagin trigger section in the policy setup) script is needed for this type of indication i.e. indications are submitted by external programs/scripts, SNMP traps.

Hybrid Indication policy (Nagin): A Hybrid (Nagin) Indication policy is used for processing text output from executables, scripts, java class or NagiosŪ like plugins(NAGINs) that are executed every specified interval. The output will be processed by the conditions specified in the Policy.

You can select between various Monitor Types:
Java
NAGIN (Executables)
Logfile Monitor
Logfile Transaction Monitor
Logfile Transaction Monitor (multiline)
(MP) Logfile Monitor
(MP) Logfile Transaction Monitor
(MP) Logfile Transaction Monitor (multiline)

Note: It is recommended to use the Multipath (MP) Logfile family instead of the "normal" monitors. These monitors are kept for backwards compatibility.


Monitor policy types

You can select between various Monitor Types:
EXEC monitor: Specify a binary or a script name relative to the Agent's plug-in directory ($BOOM_ROOT/spi/) or use '#' character at the first position to search in the global search path (e.g. #df -kl).
External: The values are submitted from some external scheduled program.
JAVA monitor: The call of the specified java class name returns the values.
OPM: Open Parser Monitor is used to convert some text output to values.