From c663aa2bf5c1b6c17d0ca38bd7fbbb405c8fead4 Mon Sep 17 00:00:00 2001
From: Michael Friedrich <michael.friedrich@netways.de>
Date: Fri, 7 Nov 2014 04:29:58 +0100
Subject: [PATCH] Documentation: Add remote client endpoint/zone config
 creation

fixes #7524
---
 doc/5-monitoring-remote-systems.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/5-monitoring-remote-systems.md b/doc/5-monitoring-remote-systems.md
index ace7d35d3..64ca91764 100644
--- a/doc/5-monitoring-remote-systems.md
+++ b/doc/5-monitoring-remote-systems.md
@@ -469,6 +469,18 @@ You can `list` and `remove` existing blacklists:
 > If you are unsure about it, set a wildcard (`*`) for them and filter only by host/services.
 
 
+### <a id="icinga2-remote-monitoring-master-manual-add-endpoint-zone"></a> Manually add Client Endpoint and Zone Objects on the Master
+
+Define a [Zone](#objecttype-zone) with a new [Endpoint](#objecttype-endpoint) similar to the cluster setup.
+
+* [configure the node name](#configure-nodename)
+* [configure the ApiListener object](#configure-apilistener-object)
+* [configure cluster endpoints](#configure-cluster-endpoints)
+* [configure cluster zones](#configure-cluster-zones)
+
+on a per remote client basis. If you prefer to synchronize the configuration to remote
+clients, you can also use the cluster provided [configuration sync](#cluster-zone-config-sync)
+in `zones.d`.
 
 
 ### <a id="agent-based-checks-addon"></a> Agent-based Checks using additional Software
-- 
2.40.0