probectl in practice — the user journeys
Start here. These are the end-to-end paths most people actually walk through probectl. Each journey is a numbered, copy-along route that stitches the underlying features together — follow one top to bottom and you'll have done a real job, not just read about a capability. The feature index is the reference behind these paths; the glossary defines any term you hit.
| Journey | What you'll achieve |
|---|---|
| J1 — Onboarding: from zero to first data | Install, enroll an agent, run your first network/HTTP/DNS test, and see real results plus a path map. |
| J2 — From alert to root cause | Set an SLO, get paged, open the correlated incident, and let the AI assistant find the grounded cause. |
| J3 — Catch a routing or security threat | Turn a BGP or NDR signal into one correlated incident, export it to your SIEM, and review a human-gated fix. |
| J4 — Stand up and isolate a tenant | Provision an isolated, white-labeled, metered tenant as a provider — with no implicit access to its data. |
| J5 — Govern cost, SLOs and sustainability | Track SLOs, egress cost, and carbon per tenant, and govern retention. |
| J6 — Operate in production | Upgrade with zero downtime, drill failover, confirm FIPS mode, and pull a support bundle. |
New to probectl? Start with J1, then follow each journey's "Next" pointer. Already running it? Jump to the journey that matches the job in front of you.