tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix Mkdocs formatting

This commit is contained in:
Michael Friedrich 2019-07-20 15:59:59 +02:00
parent 08aea595a5
commit 29e530be5a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/06-distributed-monitoring.md
View File

@ -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.