The operational problem
Private infrastructure needs a collector that can reach local sources without exposing inbound control of the network.
What you can monitor
Use a supported Windows or Linux Site Edge to collect authorized local protocols and send evidence over outbound HTTPS.
What is included
- Supported signed Windows and Linux collector packages.
- Site-scoped enrollment, heartbeats and collection-health visibility.
- Bounded collector management and update workflows with retained identity.
Plan limits and optional services are shown on the pricing page.
Coverage and requirements
Windows managed-pilot signing requires explicit IT trust. No arbitrary remote shell is offered; collector updates remain signed and bounded.
A practical workflow
- Choose a site and supported installation platform.
- Inspect the exact package, checksum and signing requirements.
- Enroll with the short-lived code through the protected setup flow.
- Wait for a real heartbeat and confirm collector capabilities.
How to set it up
- Choose a supported host with access to the intended local sources and outbound HTTPS.
- Review the installation command and signing trust, then enroll using the short-lived installation code.
- Wait for Ready, verify the heartbeat and separately configure each monitoring integration.
Collector Health: branch setup verification
Illustrative review before relying on a newly installed Site Edge.
- Identity and heartbeat
- Confirm the expected collector, site and recent communication.
- Collection health
- Inspect reported source failures and resource observations.
- Next setup step
- Activate a tested source and confirm actual telemetry; Ready alone does not mean all devices are monitored.
AOT-authored example of how to read the product. It contains no customer measurements or promised outcomes.
Reports for the decision
Collector Health reports distinguish freshness, capacity and collection failures from the health of monitored systems.
Explore report workflows →