SREs
Menu
Open workspace

Controlled incident response, accountable at every step.

Evidence before action.

SREs turns live telemetry into a defensible response—collecting what happened, proposing a bounded next move, and keeping an operator in control.

10:24:31 UTC · threshold breach corroborated by four sources

Run a safe simulation Inspect the evidence model

Simulations introduce a controlled failure in the sample environment. Production actions always require an operator.

A quiet mineral landscape framing an incident evidence excerpt
Illustrative incident · INC-4821

Checkout latency elevated

Today · 10:24:31 UTC

Investigating
Evidence excerpt4 correlated signals · read-only preview
  1. Latency threshold breached for five minutesPrometheus
  2. Checkout trace sample correlatedOpenTelemetry
  3. Error rate increased from 2.7% to 9.1%Loki
  4. Recent deploy isolated as probable causeGitHub
Human approval requiredRate-limit safeguard · reversible action
No action taken

A system that proves before it acts.

Every recommendation carries its source, sequence, expected impact, and guardrail. Operators see the whole argument—not just an answer.

Explore controlled simulations
  1. 1

    Signal

    Detect a meaningful change across metrics, logs, traces, and recent deploys.

  2. 2

    Evidence

    Correlate sources into one timestamped account with confidence and provenance.

  3. 3

    Decision

    Propose a bounded action, expose its risk, and wait for accountable approval.

See how the finding earns its confidence.

Each contribution remains attached to its source. Confidence reflects corroboration in this illustrative incident—not an unexplained model score.

Human decision remains final
  1. 01
    Prometheus

    Checkout p95 remained above the incident threshold for five minutes.

    Confidence contribution+0.40
  2. 02
    OpenTelemetry

    Slow traces converge on the checkout-api deployment path.

    Confidence contribution+0.32
  3. 03
    GitHub

    Release v2.8.4 completed ninety seconds before the first breach.

    Confidence contribution+0.22
  4. 04
    Correlated finding

    Release v2.8.4 is the probable cause. Proposed rollback remains bounded and approval-gated.

    Combined confidence0.94
Illustrative investigation artifacttrace_checkout_latency_10-24-41.jsonEvery contribution links back to timestamped source evidence.
{
  "incident": "INC-4821",
  "service": "checkout-api",
  "finding": "deploy correlated",
  "confidence": 0.94,
  "evidence": [0.40, 0.32, 0.22],
  "approval": "operator_required"
}