eventhandler

Mon, 01 Jan 0001 00:00:00 +0000

The Event Handler Framework provides a streamlined approach for writing event handler scripts in Nagios monitoring environments. With this framework, users can easily define conditions for handling events and specify actions to be taken based on those conditions, leveraging two core components: the Decider and the Runner. These components work together seamlessly to evaluate conditions, prepare parameters, and execute appropriate actions in response to events.

define command{
 command_name handle_omd_restart
 command_line $USER1$/eventhandler \
 --runner ssh \
 --runnertag omd_restart \
 --runneropt hostname='$HOSTADDRESS$' \
...
 --decider omd_site_self_heal \
 --eventopt site_name='$HOSTNAME$' \
 --eventopt HOSTNAME='$HOSTNAME$' \
 --eventopt HOSTSTATE='$HOSTSTATE$' \
 --eventopt HOSTADDRESS='$HOSTADDRESS$' \
 --eventopt SERVICEDESC='$SERVICEDESC$' \
 --eventopt SERVICESTATE='$SERVICESTATE$' \
 --eventopt SERVICEOUTPUT='$SERVICEOUTPUT$' \
 --eventopt LONGSERVICEOUTPUT='$LONGSERVICEOUTPUT$' \
 >> $USER4$/var/log/eventhandler_errors.log 2>&1

Decider

The Decider component evaluates whether an event should be handled based on the specified conditions. It considers factors such as current state, state type, attempt count, downtime, etc., and returns a set of parameters indicating the action to be taken. The binary lib/monitoring-plugins/eventhandler takes multiple --eventopt KEY=VALUE arguments, which are usually Naemon macros. These key-value pairs are found in the dict event.eventopts.

Eventhandler on ConSol Monitoring

eventhandler

Decider