e-volv

Observability playbook

ErrorBudgetReport

Weekly SLI/SLO report that computes error-budget burn rate and states the policy consequence when a budget is more than 75% consumed.

Weekly, reads SLI data for each service, computes error budget consumed against the SLO, and reports the burn rate with a projection of when the budget exhausts at the current rate. When a budget is more than 75% consumed, states plainly what the policy says happens next.

Identifier
error-budget-report
Version
1.1.0
Steps
4
Triggers
1
  • sre
  • error-budget
  • slo
  • reliability
  • weekly
  • observability

When it runs

Scheduleschedule.weekly
Schedule
Every Monday at 09:00 UTC 0 9 * * 1
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

  1. 01
    Weekly Schedule (Monday 09:00 UTC)trigger

    The event that starts the run.

  2. 02
    Fetch SLI Metrics ⚠️ ADD Authorization: Bearer <Evolve API key with metrics:read>, or point at your own metrics APIhttp.request

    Calls an external HTTP endpoint with vault-resolvable headers.

  3. 03
    Analyze Error Budgetsagent.run

    One agent works the task with its toolkit.

  4. 04
    File Error Budget Reportticket.create

    Opens a ticket on the connected tracker.

The agent

Error Budget Analyst

Base type
Senior Developer
Temperature
0.2
Max iterations
25
Tools
2

Status · 1

  • update_statusUpdate Status · write

Tickets · 1

  • create_ticketCreate Ticket · write