SUMMARIZATION

Weekly Sentry Release-Health Reliability Report to Confluence

Each week, aggregates Sentry release-health across all deploys in the period, compares aggregate error-budget burn week-over-week.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList week's releases with health metricsSentrySentry
  • ActionAggregate and compare week-over-week burnSentrySentry
  • ActionWrite narrative reliability reportOpenAI
  • OutputPublish report to ConfluenceConfluenceConfluence

What it does

Produces a weekly reliability narrative for stakeholders. It rolls up every release shipped during the week, compares aggregate crash-free rate and total error-budget burn against the prior week, calls out the worst-regressing release, and publishes a readable report to Confluence that non-engineers can follow.

When to use it

Use it when leadership or adjacent teams want a regular reliability summary and you would rather generate it than write it by hand each Friday. Pairs well with the per-deploy flows that handle real-time alerting.

How it works

  1. 1A weekly schedule triggers the flow.
  2. 2All releases deployed in the window are listed from Sentry with their health metrics.
  3. 3Aggregate crash-free and budget-burn figures are computed and compared to the previous week.
  4. 4An LLM writes a narrative report covering the week-over-week trend and the single worst regression.
  5. 5The report is published as a new Confluence page in the reliability space.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.