Add documentation for remote check queue

refs #4841

diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md
index 8cc242a832bed7ccf7ef0c2bd8d05b7c2f5dbd84..c770622ac77d70d87601825ba77dc8c88fac8866 100644 (file)
--- 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 9e2b5b3c601d83ccde94a2279ecad76aad274c66..16ef89f936d7f7ac54240e3c10e2aac48675ad1d 100644 (file)
--- 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" { }
 ```