Demo path vs. adopt path
Steps 1–3 are shared by everyone. From step 4 onward, the experience splits:- Demo path — sureops has already provisioned the integrations for your sample environment. Most steps are “acknowledge and continue” rather than requiring you to configure anything.
- Adopt path — you connect your own infrastructure at each step. Each step shows a configuration form and marks complete once the connection is verified.
The 13 steps
Step 1 — Welcome to sureops
ECHO introduces itself and gives you an overview of what the tour covers. You can begin setup or skip the welcome screen.Step 2 — Confirm your organization
Your organization name was pre-filled from your signup. This is the workspace your team shares — all incidents, problem records, and escalations belong to it. Confirm or change the name before continuing. You can update it later from Settings → Organization.Step 3 — Your environment
An environment is what sureops watches. Every integration you connect, every incident that fires, and every agent action happens in the context of an environment.- Demo path — click Provision sample environment to have sureops spin up your pre-configured sample app. This takes about 60 seconds.
- Adopt path — click Create environment and give your environment a name (e.g.,
productionorstaging).
Step 4 — Your AI model
sureops agents need an AI model to diagnose incidents, draft runbooks, and propose code fixes.- Demo path — the AI model is already configured for your demo environment under sureops’s managed boundary. No API key needed. Click Continue.
- Adopt path — provide your own API key. Without a working AI model, agents cannot diagnose incidents or propose fixes. You can skip this step and configure the key later in Settings → AI, but agents will not function until it is set.
Step 5 — Connect your telemetry
Telemetry is how sureops sees what is happening in your environment.- Demo path — telemetry is already flowing from your sample application via OpenTelemetry. Traces, metrics, and logs are wired to sureops during provisioning. Click Continue to acknowledge.
- Adopt path — connect Prometheus or Grafana. See Connect your stack for the full setup guide.
Step 6 — Connect your alert source
Incidents come from alerts. sureops listens to your existing alerting tool and does not replace it.- Demo path — your sample app’s Alertmanager is already wired to sureops via webhook. When thresholds breach, an incident opens automatically. Click Continue.
- Adopt path — connect your alert provider. The setup page shows the webhook URL to add to your Alertmanager configuration.
Step 7 — Join your war-room (Slack)
When an incident fires, sureops creates a Slack channel automatically and posts agent updates, recommendations, and approval requests there.- Demo path — a Slack channel was created for your sample environment during provisioning. Join it to watch ECHO post when an incident fires.
- Adopt path — authorize the sureops Slack app on your workspace.
Step 8 — Connect GitHub
GitHub enables two things: sureops reads your service contract from your repos, and the resolution agent opens draft fix PRs when it proposes code-level fixes.- Demo path — a fork of the sample app was created for your demo. Accept the GitHub collaborator invite to view the fork where agents open fix PRs.
- Adopt path — install the sureops GitHub App on your org and tag the repos you want sureops to access with the
sureops-managedtopic.
Step 9 — Generate your contract
The service contract is the source of truth for your service catalog — service names, owners, dependencies, runbook paths. Agents read it before every incident to understand blast radius and who to involve. Click Generate contract to have sureops read your observed services and open a draft PR with a pre-filled.sureops/services.yaml. Review it, edit anything sureops got wrong (especially ownership and tiers), and merge the PR. You can also hand-author the contract directly.
Step 10 — Discover your landscape
sureops cross-references your service contract with what is actually running in your environment. The result is a service map showing every service, its dependencies, and its deployment state. Click Generate landscape to run the discovery scan. The resulting service graph is what agents query when tracing blast radius and upstream dependencies during an incident.Step 11 — Generate your runbook
Runbooks are operational playbooks per service — agents read them during diagnosis to know what to check and what fixes are pre-approved. Click Generate runbook to have sureops draft a runbook for your most critical service and open it as a PR. An empty runbook is better than no runbook — even a skeleton with headings tells the agent where to look.Step 12 — Set up routing and escalation
When an incident fires, sureops requests HITL approval before running risky actions. This step lets you configure:- Who receives P1 approval requests (by Slack user or user group)
- Escalation timeouts — how long to wait before escalating to a backup approver
- Default approval behavior for unattended requests
- Demo path — click Use defaults to accept sureops’s recommended routing configuration.
- Adopt path — configure routing for your team.