Skip to content

srekit ebp

Generate an Error Budget Policy with tiered actions (Yellow / Orange / Red), exceptions, and escalation paths. Pairs with srekit slo.

Synopsis

srekit ebp --service NAME [flags]

Flags

Flag Required Description
--service yes Service this policy applies to

Plus the shared output flags. Default filename: ebp-<slug-of-service>.md.

Examples

srekit ebp --service api-gw --out ebp-api-gw.md

To stdout:

srekit ebp --service api-gw --stdout

Section structure

Section headings render bilingually — Russian, with the English term in parentheses. Below they are given by stable id and English term; srekit ebp --service X --json | jq -r '.sections[].title' prints them as they appear in the document.

  • Front matter: id, creation_date, modification_date, type: error-budget-policy, service, tags
  • purpose — Purpose: why the policy exists — agree on the actions before the incident, not during it
  • triggers — Triggers: a table mapping budget state to condition — Green (< 50 % spent), Yellow (50–75 %), Orange (75–100 %), Red (exhausted)
  • tiered_actions — Tiered actions: what the team actually does at Yellow / Orange / Red
  • exceptions — Exceptions
  • escalation — Escalation
  • review — Review
  • references — References

Template shape

ebp ships as a v1 YAML artifact (internal/tmpl/templates/ebp.yaml) — frontmatter, H1, meta_bullets, sections (purpose, triggers, tiered_actions, exceptions, escalation, review, references). Template expressions reference .Meta.<Field> for ID, Service, Now. See srekit postmortem for the full schema reference.

(Owner / team is a fill-in inside the rendered meta_bullets — there's no --owner flag; edit the rendered file or your customized ebp.yaml directly.)

See also