[icinga-checkins] icinga.org: icinga2/master: Docs: Small addition for endpoint explanation

git at icinga.org git at icinga.org
Mon Aug 22 10:33:48 CEST 2016


Module: icinga2
Branch: master
Commit: 4c419d099ab1ae57375690e09da18fc0243b581d
URL:    https://git.icinga.org/?p=icinga2.git;a=commit;h=4c419d099ab1ae57375690e09da18fc0243b581d

Author: Michael Friedrich <michael.friedrich at netways.de>
Date:   Mon Aug 22 09:59:44 2016 +0200

Docs: Small addition for endpoint explanation

refs #12498
refs #12386

---

 doc/6-distributed-monitoring.md |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/6-distributed-monitoring.md b/doc/6-distributed-monitoring.md
index fd2ddef..b6ce38d 100644
--- a/doc/6-distributed-monitoring.md
+++ b/doc/6-distributed-monitoring.md
@@ -25,7 +25,6 @@ Rephrasing this picture into more details:
   * A `satellite` node continues to run even if the master node is temporarily unavailable.
 * A `client` node only has a parent node.
   * A `client` node will either run its own configured checks or receive command execution events from the parent node.
-  * A `client` node will not require any further configuration after setup depending on the configuration mode [top down](6-distributed-monitoring.md#distributed-monitoring-top-down).
 
 The following sections will refer to these roles and explain the
 differences and the possibilities this kind of setup offers.
@@ -112,6 +111,9 @@ information, e.g. if the master should actively try to connect to a client.
 The zone membership is defined inside the `Zone` object definition using
 the `endpoints` attribute with an array of `Endpoint` names.
 
+If you want to check the availability (e.g. ping checks) of the node
+you still need a [Host](9-object-types.md#objecttype-host) object.
+
 ## <a id="distributed-monitoring-apilistener"></a> ApiListener
 
 In case you are using the CLI commands later, you don't have to write
@@ -912,7 +914,7 @@ If you have accidentally added specific hosts or services, you can safely purge
 them from this directory and restart Icinga 2.
 
 The generated host object uses the `cluster-zone` check command as
-[health check](distributed-monitoring-health-checks).
+[health check](6-distributed-monitoring.md#distributed-monitoring-health-checks).
 
 > **Tip** In case you want to blacklist or whitelist certain hosts and/or services
 > on the master, use the `icinga2 node {black,white}list`



More information about the icinga-checkins mailing list