Skip to main content
OpenSRE is agentic alert investigation for production systems. It connects to your observability stack, infrastructure, and knowledge bases to investigate incidents before your team gets paged — then delivers root-cause analysis and recommended fixes to Slack, PagerDuty, or local files.

Tracer to OpenSRE

Coming from Tracer? Welcome. OpenSRE is the open-source home for these docs, while some live URLs, installers, assets, and Slack app labels still use the Tracer name during the transition.

​
Get started

Quickstart

Install OpenSRE and run your first alert investigation.

Connect integrations

Wire OpenSRE into observability, incident, code, and data systems.

Run an investigation

See how OpenSRE gathers evidence and produces root cause analysis.

​
First 5 minutes

After the run completes, open the generated artifacts:
  • problem.md — incident framing
  • theory/hypothesis_*.md — hypotheses tested during the run
  • report.md — root cause, confidence, and next steps
Or export JSON for automation:
Interactive shell — run opensre with no subcommand to describe incidents in plain language and use slash commands (/help, /verify datadog, /investigate).
Stuck? See Quickstart troubleshooting (Docker running, make installed, LLM configured).

​
Start here

Investigations

Alert ingestion, evidence collection, masking, and remote runtime workflows.

Showcase

Sample outputs, quickstart demos, and CloudOpsBench benchmark walkthrough.

​
How it works

When an alert fires, OpenSRE autonomously:
  1. Ingests the alert from metrics, logs, traces, or incident systems
  2. Assembles context — ownership, deploys, dependencies, baselines
  3. Plans evidence collection across connected integrations
  4. Investigates in a loop — queries tools, updates hypotheses, stops when confidence is high enough
  5. Delivers a report to Slack, local files, or your configured messaging channel
Investigation workflow
How OpenSRE Works
See How an investigation works for a plain-language walkthrough of each stage.