Choose where it is checked from
A WebService, a TCP port or a UX test is checked from the ARGUNIS cloud or from a monitoring probe on your network.
Each Applications monitor is checked from one place. There are two options:
Option | When to use it |
|---|---|
ARGUNIS cloud | The target is public, reachable from the internet (published sites, APIs and ports). It does not reach your private network. |
Monitoring probe · name | The target is on your private network: internal APIs not exposed to the internet, intranets, internal systems and network ports. The probe checks them from inside, with no limit on how many. |
An agent only monitors its own server: it does not check WebServices, TCP ports or UX tests. That is what the monitoring probe on that network is for.
Where you choose it
On the service page, Configure → General → Monitored from (WebServices, TCP Sockets and UX tests). Changing it opens the window that shows where it moves from and to. See Change where it's monitored from.
When creating a WebService: Where it runs tab, Check from field.
When creating a TCP Socket: the form's Check from field.
When creating a UX test: Run from field. A probe needs version 3.2.0 or later for UX tests.
What the probe does
WebService: the request, the response code, the latency and the expected content; or an API monitor with steps, validations and metrics.
TCP Socket: that the port accepts connections and how long it takes.
UX test: opens a real browser inside your network.
Rules worth knowing
From the cloud only public targets are allowed: never private, local or metadata IPs, not even after a redirect.
The probe checks any target it can reach from its network.
If an old service was checked by a server's agent, it appears as not allowed in Monitored from: choose the ARGUNIS cloud or a probe on that network.