From: Michael Friedrich Date: Mon, 9 May 2016 15:42:56 +0000 (+0200) Subject: Docs: Add a note for event command execution w/ command execution bridge clients X-Git-Tag: v2.4.8~25 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0bf075baea2d9b7667a8f2ff460d855036bc32ff;p=icinga2 Docs: Add a note for event command execution w/ command execution bridge clients fixes #11742 --- diff --git a/doc/3-monitoring-basics.md b/doc/3-monitoring-basics.md index f2510a1c2..7c81fcd32 100644 --- a/doc/3-monitoring-basics.md +++ b/doc/3-monitoring-basics.md @@ -1612,6 +1612,10 @@ available through runtime vars. Runtime macros such as `$service.state_type$` and `$service.state$` will be processed by Icinga 2 helping on fine-granular events being triggered. +If you are using a client as [command execution bridge](11-icinga2-client.md#icinga2-client-configuration-command-bridge) +the event command will be executed on the client itself (similar to the check +command). + Common use case scenarios are a failing HTTP check requiring an immediate restart via event command, or if an application is locked and requires a restart upon detection. @@ -1621,7 +1625,7 @@ to support native plugin based checks. #### Use Event Commands to Restart Service Daemon -The following example will triggert a restart of the `httpd` daemon +The following example will trigger a restart of the `httpd` daemon via ssh when the `http` service check fails. If the service state is `OK`, it will not trigger any event action.