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

Fix documentation for checks inside an HA zone 

fixes #9476
This commit is contained in:
Michael Friedrich 2015-06-23 10:35:18 +02:00
parent 9e663eea4b
commit a90e2fb1a9
1 changed files with 18 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/12-distributed-monitoring-ha.md
View File

@ -582,13 +582,10 @@ Even further all commands are distributed amongst connected nodes. For example,
re-schedule a check or acknowledge a problem on the master, and it gets replicated to the re-schedule a check or acknowledge a problem on the master, and it gets replicated to the
actual slave checker node. actual slave checker node.
DB IDO on the left, graphite on the right side - works (if you disable > **Note**
[DB IDO HA](12-distributed-monitoring-ha.md#high-availability-db-ido)). >
Icinga Web 2 on the left, checker and notifications on the right side - works too. > All features must be same on all endpoints inside an [HA zone](12-distributed-monitoring-ha.md#cluster-scenarios-high-availability).
Everything on the left and on the right side - make sure to deal with > There are additional [High-Availability-enabled features](12-distributed-monitoring-ha.md#high-availability-features) available.
[load-balanced notifications and checks](12-distributed-monitoring-ha.md#high-availability-features) in a
[HA zone](12-distributed-monitoring-ha.md#cluster-scenarios-high-availability).
### <a id="cluster-scenarios-distributed-zones"></a> Distributed Zones ### <a id="cluster-scenarios-distributed-zones"></a> Distributed Zones
@ -794,19 +791,25 @@ By default the following features provide advanced HA functionality:
### <a id="high-availability-checks"></a> High Availability with Checks ### <a id="high-availability-checks"></a> High Availability with Checks
All nodes in the same zone load-balance the check execution. When one instance All instances within the same zone (e.g. the `master` zone as HA cluster) must
fails the other nodes will automatically take over the reamining checks. have the `checker` feature enabled.
> **Note** Example:
>
> If a node should not check anything, disable the `checker` feature explicitely and
> reload Icinga 2.
# icinga2 feature disable checker # icinga2 feature enable checker
# service icinga2 reload
All nodes in the same zone load-balance the check execution. When one instance shuts down
the other nodes will automatically take over the reamining checks.
### <a id="high-availability-notifications"></a> High Availability with Notifications ### <a id="high-availability-notifications"></a> High Availability with Notifications
All instances within the same zone (e.g. the `master` zone as HA cluster) must
have the `notification` feature enabled.
Example:
# icinga2 feature enable notification
Notifications are load balanced amongst all nodes in a zone. By default this functionality Notifications are load balanced amongst all nodes in a zone. By default this functionality
is enabled. is enabled.
If your nodes should notify independent from any other nodes (this will cause If your nodes should notify independent from any other nodes (this will cause
@ -821,7 +824,6 @@ have the DB IDO feature enabled.
Example DB IDO MySQL: Example DB IDO MySQL:
# icinga2 feature enable ido-mysql # icinga2 feature enable ido-mysql
The feature 'ido-mysql' is already enabled.
By default the DB IDO feature only runs on one node. All other nodes in the same zone disable By default the DB IDO feature only runs on one node. All other nodes in the same zone disable
the active IDO database connection at runtime. The node with the active DB IDO connection is the active IDO database connection at runtime. The node with the active DB IDO connection is