2014-05-04 18:49:09 +02:00
# <a id="monitoring-remote-systems"></a> Monitoring Remote Systems
2014-05-04 11:25:12 +02:00
2015-03-07 15:52:56 +01:00
## <a id="monitoring-remote-systems-overview"></a> Overview
2014-11-02 20:35:16 +01:00
2015-03-07 15:52:56 +01:00
There's a variety of possibilities to monitor remote servers and services. First off you should
decide how your primary monitoring master is able to reach these hosts and services.
2014-11-02 20:35:16 +01:00
2015-03-07 15:52:56 +01:00
* direct connection querying the service interface (for example `http` ), so-called [agent-less checks ](9-monitoring-remote-systems.md#agent-less-checks )
* local checks requiring an additional daemon as communication device for your monitoring server
2014-11-02 20:35:16 +01:00
2014-05-04 11:25:12 +02:00
## <a id="agent-less-checks"></a> Agent-less Checks
If the remote service is available using a network protocol and port,
2015-01-22 09:40:25 +01:00
and a [check plugin ](2-getting-started.md#setting-up-check-plugins ) is available, you don't
2014-05-04 11:25:12 +02:00
necessarily need a local client installed. Rather choose a plugin and
2015-02-11 11:51:58 +01:00
configure all parameters and thresholds. The [Icinga 2 Template Library ](7-icinga-template-library.md#icinga-template-library )
2014-11-02 20:35:16 +01:00
already ships various examples like
2015-02-11 11:51:58 +01:00
* [ping4 ](7-icinga-template-library.md#plugin-check-command-ping4 ), [ping6 ](7-icinga-template-library.md#plugin-check-command-ping6 ),
[fping4 ](7-icinga-template-library.md#plugin-check-command-fping4 ), [fping6 ](7-icinga-template-library.md#plugin-check-command-fping6 ), [hostalive ](7-icinga-template-library.md#plugin-check-command-hostalive )
* [tcp ](7-icinga-template-library.md#plugin-check-command-tcp ), [udp ](7-icinga-template-library.md#plugin-check-command-udp ), [ssl ](7-icinga-template-library.md#plugin-check-command-ssl )
* [http ](7-icinga-template-library.md#plugin-check-command-http ), [ftp ](7-icinga-template-library.md#plugin-check-command-ftp )
* [smtp ](7-icinga-template-library.md#plugin-check-command-smtp ), [ssmtp ](7-icinga-template-library.md#plugin-check-command-ssmtp ),
[imap ](7-icinga-template-library.md#plugin-check-command-imap ), [simap ](7-icinga-template-library.md#plugin-check-command-simap ),
[pop ](7-icinga-template-library.md#plugin-check-command-pop ), [spop ](7-icinga-template-library.md#plugin-check-command-spop )
* [ntp_time ](7-icinga-template-library.md#plugin-check-command-ntp-time )
* [ssh ](7-icinga-template-library.md#plugin-check-command-ssh )
* [dns ](7-icinga-template-library.md#plugin-check-command-dns ), [dig ](7-icinga-template-library.md#plugin-check-command-dig ), [dhcp ](7-icinga-template-library.md#plugin-check-command-dhcp )
2014-11-02 20:35:16 +01:00
There are numerous check plugins contributed by community members available
2015-01-22 09:40:25 +01:00
on the internet. If you found one for your requirements, [integrate them into Icinga 2 ](3-monitoring-basics.md#command-plugin-integration ).
2014-11-02 20:35:16 +01:00
Start your search at
* [Icinga Exchange ](https://exchange.icinga.org )
* [Icinga Wiki ](https://wiki.icinga.org )
2014-11-15 13:53:37 +01:00
An example is provided in the sample configuration in the getting started
2015-06-16 16:01:02 +02:00
section provided by Icinga 2 ([hosts.conf](4-configuring-icinga-2.md#hosts-conf), [services.conf ](4-configuring-icinga-2.md#services-conf )).
2014-11-02 20:35:16 +01:00
2014-11-15 13:53:37 +01:00
2015-03-07 15:52:56 +01:00
## <a id="agent-based-checks"></a> Agent-based Checks
2014-05-04 11:25:12 +02:00
If the remote services are not directly accessible through the network, a
local agent installation exposing the results to check queries can
become handy.
2015-03-07 15:52:56 +01:00
Icinga 2 itself can be used as agent (client, satellite) in this scenario, but there
are also a couple of addons available for this task.
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
The most famous ones are listed below.
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
## <a id="agent-based-checks-linux-unix"></a> Agent-based Checks for Linux/Unix
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
The agent runs as daemon and communicates with the master requesting a check being executed
or local stored information (SNMP OID). The Icinga 2 client continues to execute checks
when the connection dies, and does not need the master as check scheduler like the other
listed agents.
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
* Icinga 2 Client
* SSH
* SNMP
* NRPE
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
## <a id="agent-based-checks-windows"></a> Agent-based Checks for Windows
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
The Windows agent runs as administrative service and offers direct plugin execution and/or
local check result being sent to the master instance.
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
* Icinga 2 Client
* NSClient++
2014-08-24 11:21:54 +02:00
2015-03-07 15:52:56 +01:00
SNMP could also be used, but was deprecated in Windows Server 2012. Alternatively you can
look into the WMI interface.
2014-08-24 11:21:54 +02:00