From 6df6f72a3539ba8bdbd3d1a0a18d507763afe133 Mon Sep 17 00:00:00 2001 From: Noah Hilverling Date: Mon, 29 Jan 2018 14:40:40 +0100 Subject: [PATCH] Add documentation for remote check queue refs #4841 --- doc/06-distributed-monitoring.md | 4 ++++ doc/09-object-types.md | 2 -- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md index 8cc242a83..c770622ac 100644 --- a/doc/06-distributed-monitoring.md +++ b/doc/06-distributed-monitoring.md @@ -818,6 +818,10 @@ This mode will force the Icinga 2 node to execute commands remotely on a specifi The host/service object configuration is located on the master/satellite and the client only needs the CheckCommand object definitions being used there. +Every endpoint has its own remote check queue. The amount of checks executed simultaneously +can be limited on the endpoint with the `MaxConcurrentChecks` constant defined in [constants.conf](04-configuring-icinga-2.md#constants-conf). Icinga 2 may discard check requests, +if the remote check queue is full. + ![Icinga 2 Distributed Top Down Command Endpoint](images/distributed-monitoring/icinga2_distributed_top_down_command_endpoint.png) Advantages: diff --git a/doc/09-object-types.md b/doc/09-object-types.md index 9e2b5b3c6..16ef89f93 100644 --- a/doc/09-object-types.md +++ b/doc/09-object-types.md @@ -247,8 +247,6 @@ This configuration object is available as [checker feature](11-cli-commands.md#c Example: ``` -library "checker" - object CheckerComponent "checker" { } ``` -- 2.49.0