Where each thing is monitored from
What the ARGUNIS cloud reaches, what a monitoring probe reaches and what a server's agent reaches, so you can choose the right one.
On this page
ARGUNIS checks your hosts and services from three places. Each one reaches different things: choose the one that reaches the target.
The three places
From | What it monitors | What it does not monitor |
|---|---|---|
ARGUNIS cloud | The perimeter and whatever is queried through an API from the internet: cloud services (Railway and others), costs (FinOps), WebServices, TCP ports and UX tests of internet-facing pages. | Nothing inside your private network: no servers, network devices, internal databases or intranet pages. It does not run plugins. |
Monitoring probe | Everything it can reach from the network where it is installed: servers, network devices (SNMP), printers, databases, internal WebServices and APIs not exposed to the internet, TCP ports, UX tests of internal (intranet) pages, discovery and topology. It runs plugins. | Networks it can't reach. |
Server agent | The operating system it is installed on (Linux with systemd or Windows; if that Linux runs inside a container, it sees that Linux): CPU, memory, disks, services, logs, containers and databases. It runs your company's plugins on that system, like Nagios agents, with the interpreters it already has (bash, Python, Perl, PowerShell). | Other hosts on the network, WebServices, TCP ports and UX tests (those belong to the cloud or the probe) and catalog plugins. It is not installed as a container nor, for now, on macOS. |
How to choose
Is the target public on the internet (an API, a site, a cloud service)? → ARGUNIS cloud. If it is an internal API, site or port → the Monitoring probe for that network. A UX test of an internal (intranet) page cannot be done from the cloud: run it from the monitoring probe for that network (version 3.2.0 or later).
Is it inside your network (a server, a switch, a printer, a database)? → the Monitoring probe for that network.
Is it the same server and do you want more detail (processes, logs, services)? → the Agent on that server.
Plugins (for example, check_oracle_health) are run only by the probe and the agent. The ARGUNIS cloud doesn't run them: that way it can never reach private networks.