Guides

These guides walk through the most common things you do as an operator: configuring your first health check, connecting a satellite, wiring up notifications, setting up SSO, managing teams, opening and resolving incidents, scheduling maintenance, installing plugins, getting started with GitOps, and silencing alerts during a known disruption.

If you are looking for the mental model behind these workflows, read the Concepts section first.

Set up your first health checkFrom a blank install: create a system, attach an HTTP check, see the first result land.

Connect a satelliteMint a token, boot the satellite container, and pin checks to a remote vantage point.

Wire up Slack notificationsInstall the Slack plugin, register a webhook, and subscribe a system to it.

Configure SAML SSOConnect Checkstack to Okta or any SAML 2.0 IdP and map directory groups to roles.

Configure LDAPConnect Checkstack to LDAP or Active Directory and map memberOf groups to roles.

Create your first teamGroup users, grant the team access to specific resources, and verify scoping.

Open and resolve an incidentManually walk an incident from investigating through resolved, with status updates.

Schedule a maintenance windowPre-arm a planned disruption with suppression, post updates, and resolve cleanly.

Install a pluginInstall a plugin from npm, GitHub release, or a tarball upload via the Plugin Manager.

GitOps quickstartConnect a Git repo, push a YAML descriptor, and watch the reconciler create the entity.

Silence alerts during an incidentThree ways to silence: incident suppression, maintenance windows, per-subscription mute.

Monitor a service across staging and productionCreate environments, attach a system, and write one HTTP check that fans out per environment using config templating.