-# Distributed Monitoring with Master, Satellites
, and Clients <a id="distributed-monitoring"></a>
+# Distributed Monitoring with Master, Satellites
and Agents <a id="distributed-monitoring"></a>
This chapter will guide you through the setup of a distributed monitoring
environment, including high-availability clustering and setup details
for Icinga masters, satellites and agents.
-## Roles: Master, Satellites
, and Clients <a id="distributed-monitoring-roles"></a>
+## Roles: Master, Satellites
and Agents <a id="distributed-monitoring-roles"></a>
Icinga 2 nodes can be given names for easier understanding:
* A `satellite` node which is a child of a `satellite` or `master` node.
* An `agent` node which is connected to `master` and/or `satellite` nodes.
-
+
Rephrasing this picture into more details:
The Icinga 2 hierarchy consists of so-called [zone](09-object-types.md#objecttype-zone) objects.
Zones depend on a parent-child relationship in order to trust each other.
-
+
Have a look at this example for the `satellite` zones which have the `master` zone as a parent zone:
Nodes which are a member of a zone are so-called [Endpoint](09-object-types.md#objecttype-endpoint) objects.
-
+
Here is an example configuration for two endpoints in different zones:
this should be the FQDN.
```
-Starting the Client/Satellite setup routine...
+Starting the Agent/Satellite setup routine...
Please specify the common name (CN) [icinga2-agent1.localdomain]: icinga2-agent1.localdomain
```
uses this transport method.
-#### Finish Windows
Client Setup <a id="distributed-monitoring-setup-agent-windows-finish"></a>
+#### Finish Windows
Agent Setup <a id="distributed-monitoring-setup-agent-windows-finish"></a>
Finish the Windows setup wizard.
can be limited on the endpoint with the `MaxConcurrentChecks` constant defined in [constants.conf](04-configuration.md#constants-conf). Icinga 2 may discard check requests,
if the remote check queue is full.
-
+
Advantages:
and sync the satellite checks (disk, memory, etc.). The satellites run their
own local scheduler and will send the check result messages back to the master.
-
+
Advantages:
and IDO database backend and uses the [command endpoint mode](06-distributed-monitoring.md#distributed-monitoring-top-down-command-endpoint)
to execute checks on the remote agents.
-
+
* `icinga2-master1.localdomain` is the primary master node.
* `icinga2-agent1.localdomain` and `icinga2-agent2.localdomain` are two child nodes as agents.
<!-- Keep this for compatibility -->
<a id="distributed-monitoring-scenarios-ha-master-clients"></a>
-### High-Availability Master with
Clients <a id="distributed-monitoring-scenarios-ha-master-agents"></a>
+### High-Availability Master with
Agents <a id="distributed-monitoring-scenarios-ha-master-agents"></a>
This scenario is similar to the one in the [previous section](06-distributed-monitoring.md#distributed-monitoring-master-agents). The only difference is that we will now set up two master nodes in a high-availability setup.
These nodes must be configured as zone and endpoints objects.
-
+
The setup uses the capabilities of the Icinga 2 cluster. All zone members
replicate cluster events between each other. In addition to that, several Icinga 2
satellites receiving their configuration from the master zone, and agents checked via command
endpoint from the satellite zones.
-
+
> **Tip**:
>
connection from the Icinga agent only. Remote connections to the HTTP API
are not recommended with using the legacy HTTP API.
-### Windows
Client and Plugins <a id="distributed-monitoring-windows-plugins"></a>
+### Windows
Agent and Plugins <a id="distributed-monitoring-windows-plugins"></a>
The Icinga 2 package on Windows already provides several plugins.
Detailed [documentation](10-icinga-template-library.md#windows-plugins) is available for all check command definitions.
Open Icinga Web 2 and check your newly added Windows disk check :)
-
+
If you want to add your own plugins please check [this chapter](05-service-monitoring.md#service-monitoring-requirements)
for the requirements.
-### Windows
Client and NSClient++ <a id="distributed-monitoring-windows-nscp"></a>
+### Windows
Agent and NSClient++ <a id="distributed-monitoring-windows-nscp"></a>
There are two methods available for querying NSClient++:
Two new services ("nscp-drive-D:" and "nscp-drive-C:") will be visible in Icinga Web 2.
-
+
Note: You can also omit the `command_endpoint` configuration to execute
the command on the master. This also requires a different value for `nscp_api_host`
Open Icinga Web 2 and check your newly added Windows NSClient++ check :)
-
+
> **Tip**
>
projects / icinga2 / commitdiff
