tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: Add a note for event command execution w/ command execution bridge clients 

fixes #11742
This commit is contained in:
Michael Friedrich 2016-05-09 17:42:56 +02:00
parent 8a65c4a776
commit e3ddccc867
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/3-monitoring-basics.md
View File

@ -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 and `$service.state$` will be processed by Icinga 2 helping on fine-granular
events being triggered. 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 Common use case scenarios are a failing HTTP check requiring an immediate
restart via event command, or if an application is locked and requires restart via event command, or if an application is locked and requires
a restart upon detection. a restart upon detection.
@ -1621,7 +1625,7 @@ to support native plugin based checks.
#### <a id="event-command-restart-service-daemon"></a> Use Event Commands to Restart Service Daemon #### <a id="event-command-restart-service-daemon"></a> 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 via ssh when the `http` service check fails. If the service state is
`OK`, it will not trigger any event action. `OK`, it will not trigger any event action.