SUMMARIZATION

Monthly Reliability Board Summary from Honeycomb + Datadog

Once a month, blends Honeycomb trace/SLO data with Datadog uptime metrics into a single executive reliability summary and emails it as a board-ready brief.

CategorySummarization
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFirst-business-day monthly schedule
  • ActionPull 30-day SLO burn + slow traces from HoneycombHoneycomb
  • ActionPull availability + incident counts from DatadogDatadogDatadog
  • LogicReconcile trace vs metric reliability, flag mismatches
  • ActionWrite board-ready reliability brief with risk outlookOpenAI
  • OutputEmail brief to leadership distribution listGmailGmail

What it does

Produces a monthly, board-level reliability summary by combining two sources: Honeycomb for trace-derived SLO burn and latency outliers, and Datadog for top-line availability and incident counts. The output is a concise narrative in business language — overall availability, budget consumed across the month, notable incidents, and a forward-looking risk note.

When to use it

Run it ahead of monthly board prep or a leadership review when someone needs a defensible reliability story stitched from more than one tool. It removes the manual screenshot-and-paste cycle of building the slide every month.

How it works

  1. 1A monthly schedule fires on the first business day.
  2. 2It pulls trailing-30-day SLO burn and slow-trace summaries from Honeycomb.
  3. 3It pulls availability percentage and incident counts from Datadog for the same window.
  4. 4A logic step reconciles the two — flagging any disagreement between trace-based and metric-based reliability.
  5. 5An LLM step writes the board-ready brief with a risk outlook.
  6. 6The brief is emailed to the leadership distribution list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HoneycombDistributed traces and queries.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.