Docs
What BurnRateSurgeon replays, what it can tell you about a burn-rate rule, and where to start.
What brs does
brs replay takes a TSDB snapshot and a rules file — Prometheus recording and alerting rules, optionally an Alertmanager config, or a single Datadog export bundle — and simulates the alert evaluation deterministically over the recorded window. The output is a Markdown report: which alerts would have fired, when, and — for every alert that has a root-cause finding — which of the six canonical failure classes it maps to.
Two vendor shapes, one report
A scenario comes from one vendor at a time. Prometheus needs a TSDB snapshot and a rules file; Datadog needs one export bundle. Both produce the same report shape, so a rule migrated from one vendor to the other can be replayed against its own history either way.
brs replay --tsdb ./snapshot --rules rules.yml --alertmanager alertmanager.ymlbrs replay --datadog ./export.jsonWhere to start
- Quickstart — build the CLI from source and replay your first snapshot.
- CLI reference — every flag
brs replayaccepts, and the exit codes a CI pipeline can key off. - A forensic case study — one root-cause class, replayed end to end.