Change where it's monitored from
Move a server between the ARGUNIS cloud, a probe, and its agent, or a WebService, TCP check, or UX test between the cloud and a probe, without losing its history.
Everything ARGUNIS monitors has a single source: the ARGUNIS cloud, a monitoring probe on your network or, only for the server itself, its agent. You can change it whenever you want; ARGUNIS migrates the monitoring, and the page, history, and metrics carry over.
Where
On the page, click Configure and, in the General tab, choose in Monitored from. It works the same for servers and hosts, WebServices, TCP Sockets, and UX tests.
When you choose another source, a window opens that shows Today → Moves to and what will happen. Nothing changes until you confirm.
Servers and hosts
From → to | What happens |
|---|---|
One probe → another probe | Click Move to the probe: the configuration (protocol, credential, logs, checks, and plugins) moves as is to the other probe. |
The cloud → a probe | Click Continue: Monitor from the probe opens with the probe already chosen so you can complete the protocol and credential. It's applied when you save. |
An agent → a probe | Same as the previous one. When you save, the agent is removed from ARGUNIS (uninstall it from the server) and whatever was checked from it becomes inactive, with its history. |
A probe or the cloud → the agent | Click Install the agent: the agent installation for that server opens, with its command for Linux or Windows. Until it connects, the server keeps being checked as it is today. When it connects, the agent takes over the server with the same page and history; the probe setup is kept and turned off, so you can go back to it if needed. While it waits, the page says "The agent … is waiting to be installed on this server". |
A probe → the cloud | Click Move to the cloud: the probe stops checking it and it's checked again via SSH or SNMP from the internet. Only for hosts exposed to the internet. |
A probe's own server, hosts that come from an integration, and platform servers don't change source.
WebServices, TCP Sockets, and UX tests
They are checked from the ARGUNIS cloud or from a monitoring probe; never from an agent (an agent only monitors its own server). Choose the new source and click Change the source: the next checks run from there within seconds.
The cloud only reaches what is exposed to the internet.
For internal APIs, sites, or ports that aren't exposed to the internet, choose the probe on that network (for UX tests, probe 3.2.0 or later).
If an agent was checking it before, it appears as not allowed: change it to the cloud or a probe.