Docs
Documentation
Get an agent reporting in a few minutes, then wire the data into whatever you already run.
Start here
- Install the agent — packages, enrolment, first checks.
- Collector topology — how a region reaches aggregation,
and what runs on
api.srvpulse.net. - HTTP API — read metrics, manage checks, export.
Concepts
Agent
One process per host. Collects locally, batches every few seconds, and holds one connection to its region's collector. No inbound ports, no credentials on disk after enrolment.
Collector
A regional endpoint that terminates agent connections and forwards upstream. Collectors are stateless apart from their spool directory; losing one moves its agents to the next nearest region on reconnect.
Aggregation endpoint
Where collectors send their batches. It is not reachable by agents and accepts connections only from enrolled collectors.
Workspace
Billing and access boundary. Agents, collectors and API tokens all belong to exactly one.
Browsing a collector or aggregation endpoint serves this documentation and
nothing else — the console lives at
app.srvpulse.net.Plan limits
| Limit | Team | Scale |
|---|---|---|
| Hosts | 50 | unlimited |
| Minimum interval | 30s | 10s |
| Retention | 30d | 13 months |
| Private collectors | 1 | unlimited |
| Ingest per collector | 5 000 samples/s | 50 000 samples/s |