Browse documentation
Server dependencies and monitoring
↩ Servers
Two tabs on the server detail page help you understand how a server is watched and what relies on it: Monitoring and Dependencies.
The Monitoring tab
This tab is the single place to see how a server is collected and when it was last seen. It shows:
- Collection method — whether the server is monitored by an agent, agentlessly (SSH / WMI / Proxmox API, with the profile name), by ICMP only, or not monitored.
- ICMP monitoring — the assigned ICMP profile and its poll interval.
- Scanning profile — the profile name, type, and intervals (or a note that collection is via the agent).
- Last activity — last seen, last successful scan, and last package scan timestamps.
For agentless servers, a Scan now button (in the page header) triggers an immediate poll; it's unavailable if the server has no scanning profile or address.
The Dependencies tab
The Dependencies tab records relationships between this server and other infrastructure — what it depends on, and what depends on it. Mapping dependencies helps you understand impact: if a server goes down, you can see what else is affected.
Dependencies are also used by the redundancy-aware impact view — see Understanding redundancy-aware impact.
Editing monitoring settings
Use Edit on the server to change its type, connection address, scanning profile, ICMP profile, hypervisor link, or notes. Changing profiles here is how you switch or adjust the collection method.
Notes & tips
- Last seen and last successful scan are shown separately on purpose — a server can be reachable (last seen recent) while a full scan is older.
- Pair server dependencies with alerts so the right people hear about an outage that affects downstream systems.