1 # <a id="monitoring-remote-systems"></a> Monitoring Remote Systems
3 ## <a id="monitoring-remote-systems-overview"></a> Overview
5 There's a variety of possibilities to monitor remote servers and services. First off you should
6 decide how your primary monitoring master is able to reach these hosts and services.
8 * direct connection querying the service interface (for example `http`), so-called [agent-less checks](10-monitoring-remote-systems.md#agent-less-checks)
9 * local checks requiring an additional daemon as communication device for your monitoring server
11 ## <a id="agent-less-checks"></a> Agent-less Checks
13 If the remote service is available using a network protocol and port,
14 and a [check plugin](2-getting-started.md#setting-up-check-plugins) is available, you don't
15 necessarily need a local client installed. Rather choose a plugin and
16 configure all parameters and thresholds. The [Icinga 2 Template Library](7-icinga-template-library.md#icinga-template-library)
17 already ships various examples like
19 * [ping4](7-icinga-template-library.md#plugin-check-command-ping4), [ping6](7-icinga-template-library.md#plugin-check-command-ping6),
20 [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)
21 * [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)
22 * [http](7-icinga-template-library.md#plugin-check-command-http), [ftp](7-icinga-template-library.md#plugin-check-command-ftp)
23 * [smtp](7-icinga-template-library.md#plugin-check-command-smtp), [ssmtp](7-icinga-template-library.md#plugin-check-command-ssmtp),
24 [imap](7-icinga-template-library.md#plugin-check-command-imap), [simap](7-icinga-template-library.md#plugin-check-command-simap),
25 [pop](7-icinga-template-library.md#plugin-check-command-pop), [spop](7-icinga-template-library.md#plugin-check-command-spop)
26 * [ntp_time](7-icinga-template-library.md#plugin-check-command-ntp-time)
27 * [ssh](7-icinga-template-library.md#plugin-check-command-ssh)
28 * [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)
30 There are numerous check plugins contributed by community members available
31 on the internet. If you found one for your requirements, [integrate them into Icinga 2](3-monitoring-basics.md#command-plugin-integration).
35 * [Icinga Exchange](https://exchange.icinga.org)
36 * [Icinga Wiki](https://wiki.icinga.org)
38 An example is provided in the sample configuration in the getting started
39 section provided by Icinga 2 ([hosts.conf](4-configuring-icinga-2.md#hosts-conf), [services.conf](4-configuring-icinga-2.md#services-conf)).
42 ## <a id="agent-based-checks"></a> Agent-based Checks
44 If the remote services are not directly accessible through the network, a
45 local agent installation exposing the results to check queries can
48 Icinga 2 itself can be used as agent (client, satellite) in this scenario, but there
49 are also a couple of addons available for this task.
51 The most famous ones are listed below.
53 ## <a id="agent-based-checks-linux-unix"></a> Agent-based Checks for Linux/Unix
55 The agent runs as daemon and communicates with the master requesting a check being executed
56 or local stored information (SNMP OID). The Icinga 2 client continues to execute checks
57 when the connection dies, and does not need the master as check scheduler like the other
65 ## <a id="agent-based-checks-windows"></a> Agent-based Checks for Windows
67 The Windows agent runs as administrative service and offers direct plugin execution and/or
68 local check result being sent to the master instance.
73 SNMP could also be used, but was deprecated in Windows Server 2012. Alternatively you can
74 look into the WMI interface.