THE METHOD · SALVO v0.9APRIL MMXXVI

How it correlates.

Six stages from alert firehose to drafted runbook. Every stage is inspectable; no stage hides behind an LLM call.

  1. 01
    Stream

    Subscribe to alerts.

    Salvo connects to Prometheus, Datadog, Grafana, or a plain webhook. No agent to install; no sidecar to inject.

  2. 02
    Cluster

    Collapse correlated alerts.

    Temporal + service + label correlation; 42 alerts from one P0 event become one incident, not forty PagerDuty pages.

  3. 03
    Graph

    Build the incident graph.

    Alerts emit from services. Services depend on services. The graph is derived from your service mesh and deploy pipeline — not guessed.

  4. 04
    Hypothesize

    Score candidate causes.

    Deploys, schema migrations, traffic changes, upstream partial outages — each is a candidate with an evidence path and a confidence score. Salvo never picks one silently.

  5. 05
    Draft

    Write a runbook.

    For the top candidate, Salvo drafts an ordered runbook. Every step has a confidence score. Every mitigation is copy-to-clipboard; the agent never executes.

  6. 06
    Sign

    Timeline + postmortem stub.

    The incident closes with a signed timeline (who-did-what, salvo-vs-human) and a pre-populated postmortem doc. You write the narrative; Salvo owns the scaffolding.

What we won't do
  • — Auto-mitigate. The agent never runs kubectl.
  • — Auto-resolve. An incident closes when a human closes it.
  • — Ship a cause without an evidence path.
  • — Require a data-platform team to install us.
Open console