From 29e530be5a498ebfcc81e2ddd135064b73ac9f5b Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Sat, 20 Jul 2019 15:59:59 +0200 Subject: [PATCH] Fix Mkdocs formatting --- doc/06-distributed-monitoring.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md index 917ea3cc8..ca200ae5c 100644 --- a/doc/06-distributed-monitoring.md +++ b/doc/06-distributed-monitoring.md @@ -17,14 +17,14 @@ Icinga 2 nodes can be given names for easier understanding: Rephrasing this picture into more details: * A `master` node has no parent node. - * A `master`node is where you usually install Icinga Web 2. - * A `master` node can combine executed checks from child nodes into backends and notifications. + * A `master`node is where you usually install Icinga Web 2. + * A `master` node can combine executed checks from child nodes into backends and notifications. * A `satellite` node has a parent and a child node. - * A `satellite` node may execute checks on its own or delegate check execution to child nodes. - * A `satellite` node can receive configuration for hosts/services, etc. from the parent node. - * A `satellite` node continues to run even if the master node is temporarily unavailable. + * A `satellite` node may execute checks on its own or delegate check execution to child nodes. + * A `satellite` node can receive configuration for hosts/services, etc. from the parent node. + * A `satellite` node continues to run even if the master node is temporarily unavailable. * An `agent` node only has a parent node. - * An `agent` node will either run its own configured checks or receive command execution events from the parent node. + * An `agent` node will either run its own configured checks or receive command execution events from the parent node. A client can be a secondary master, a satellite or an agent. It typically requests something from the primary master or parent node.