On-prem collectors
Monitor servers and apps behind a firewall through one collector per site, over a single outbound connection.
Shows up in API Monitoring, Traces, Logs
How to connect
- Choose Add collector and name the site. You get an enrollment token, valid once for 24 hours.
- Install the collector on one machine at that site. It needs no admin rights and only connects out over port 443, so no firewall change.
- Install the probe on each server you want watched. Apps need nothing new: point their OpenTelemetry exporter at the collector.
Why one collector per site
Only the collector holds a credential, so there is one secret per site instead of one per server, and a site that stops reporting shows up as one row below instead of silence.
- Collector: one per site, listens on your LAN only, and spools to disk so a cloud outage loses nothing.
- Probe: one per server. It runs as administrator to read kernel network data (eBPF), holds no credential and writes nothing to disk.
- Credentials: the enrollment token is single-use; the collector’s own credential lasts until you revoke it here.
Collectors
One row per site. “Reporting” means heartbeating now, not merely enrolled — a collector whose machine was switched off last week still counts as enrolled
No matching results
Servers reporting
The fleet, flattened. A collector row says “three servers”; this says which three — the question asked the moment one of them goes quiet
No matching results
