Skip to content

Monitoring & compliance

Keep an eye on whether things are up and whether they're configured the way they should be.

In this section

Page What it's for
Monitoring Run health checks (ping, TCP, HTTP, and more) against IPs and subnets, with schedules, history, and alerts.
Outposts Remote check engines for networks Danbyte can't reach directly.
Zabbix Let an existing Zabbix answer for a scope's monitoring status. Off by default.
PRTG monitoring Connect an existing PRTG core server and test what Danbyte can read. Off by default.
SNMP discovery Walk devices for interfaces, neighbors and facts, and reconcile drift.
Certificate inventory Record the TLS certificates your endpoints actually serve - expiry, issuer, SANs, key strength. Public data only; never a private key.
SSH host keys Capture and track the host keys your devices present.
Device access Connect protocols and the opt-in in-browser SSH terminal.
Compliance Define rules your objects must satisfy, and see what's violating them.
Known vulnerabilities Match your inventory against NVD, OSV and Microsoft advisory data. Off by default.
Discovery Read installed packages over SSH or WinRM and scan TCP ports of IPAM addresses, under an authorised profile. Off by default; its own section of these docs.

Background workers and the scheduler live under Background jobs (Working with data).