Protocol and journey coverage
Monitor HTTP/API, browser, TCP, DNS, ICMP, TLS, gRPC, and heartbeat paths from one inventory.
Run active protocol and browser checks from the Standalone embedded runner or your own private Probe locations. Test every draft, publish a verified revision, and keep schedule, state, and execution evidence connected.
Protocol breadth matters only when targets, credentials, schedules, and failures remain governable.
Monitor HTTP/API, browser, TCP, DNS, ICMP, TLS, gRPC, and heartbeat paths from one inventory.
Create a draft, run a real test, and publish only after the target and assertions succeed.
Start locally in Standalone, then register open-source Probe Agents in private networks or regions.
Keep credentials write-only and enforce address policy before a Probe can reach a target.
workflow
The active schedule never changes until its replacement has produced usable evidence.
Set protocol-specific input, warning and critical assertions, timeout, retries, and location policy.
Inspect resolution, attempts, timings, response evidence, and assertion failures before scheduling.
Publish the tested revision and let the scheduler calculate the next due time.
Review multi-location evidence, run on demand, or feed a sustained failure into status-page automation.
proof / shipped
Standalone includes an embedded runner, while the open-source Probe Agent uses one-time registration and an mTLS control stream.
Run active protocol and browser checks from the Standalone embedded runner or your own private Probe locations. Test every draft, publish a verified revision, and keep schedule, state, and execution evidence connected.