> ## Documentation Index
> Fetch the complete documentation index at: https://opensre.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Showcase

> Real-world OpenSRE workflows, sample outputs, and community examples

Concrete examples of what OpenSRE looks like in practice — from install through root-cause analysis.

## Quickstart walkthrough

Install, onboard, and run your first investigation in under ten minutes.

<CardGroup cols={2}>
  <Card title="Follow the quickstart" icon="rocket" href="/docs/quickstart">
    Step-by-step install, onboarding, and sample alert investigation.
  </Card>

  <Card title="Watch install + onboard" icon="play" href="/docs/quickstart#install-opensre">
    GIF walkthroughs for macOS, Linux, and Windows.
  </Card>
</CardGroup>

<Frame>
  <img src="https://mintcdn.com/tracer/p9QMaHUNKBbW3kp5/images/quickstart-investigate.gif?s=879ef2fc978da1f592e1d938d7ac6b4a" alt="Running an OpenSRE investigation on a sample alert through to a structured root-cause report" width="790" height="560" data-path="images/quickstart-investigate.gif" />
</Frame>

Typical first-run commands:

```bash theme={null}
curl -fsSL https://install.opensre.com | bash
opensre onboard
opensre investigate -i tests/e2e/kubernetes/fixtures/datadog_k8s_alert.json
```

## Sample investigation output

A completed local run writes structured RCA artifacts you can open in any editor:

| File                     | What it contains                                                 |
| ------------------------ | ---------------------------------------------------------------- |
| `problem.md`             | Incident framing, impacted components, initial hypothesis        |
| `theory/hypothesis_*.md` | Each hypothesis tested during the run, with supporting evidence  |
| `report.md`              | Final root-cause summary, confidence, and recommended next steps |

Export a single JSON file for automation:

```bash theme={null}
opensre investigate -i <alert-file> --output ./rca.json
```

See [Investigations overview](/docs/investigation-overview) for the full workflow, slash commands, and Slack delivery.

<Frame>
  <img src="https://mintcdn.com/tracer/6RQuWf9hpcHFPckz/images/slack_alert.png?fit=max&auto=format&n=6RQuWf9hpcHFPckz&q=85&s=b9f4eb4f00a3e38d694d245377c8489a" alt="Slack incident summary after an OpenSRE investigation" width="1678" height="1954" data-path="images/slack_alert.png" />
</Frame>

## Benchmark: CloudOpsBench

Run OpenSRE against the 452-scenario CloudOpsBench Kubernetes RCA corpus and compare to published LLM-alone baselines.

```bash theme={null}
uv run python -m tests.benchmarks._framework.cli run \
  --config tests/benchmarks/cloudopsbench/config.yaml \
  --models claude-sonnet-4-20250514
```

See [CloudOpsBench benchmark](/docs/cloudopsbench) for configuration, integrity guards, and cost tracking.

## Share your work

Have a demo, runbook, or incident post-mortem powered by OpenSRE?

1. Open a [GitHub Discussion](https://github.com/Tracer-Cloud/opensre/discussions) with the tag **Showcase** — include commands, integrations used, and (if possible) redacted output.
2. Join the [bi-weekly giveaway](/docs/bi-weekly-giveaway) for a chance to win OpenSRE swag when you share what you built.