SUMMARIZATION

Weekly Honeycomb Trace Trend Report to Notion

Once a week, aggregates seven days of Honeycomb trace metrics, has OpenAI write a narrative trend report on latency and error movement per service.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires Monday morning
  • ActionAggregate 7 days of latency and error metrics per serviceHoneycomb
  • ActionWrite narrative week-over-week trend reportOpenAI
  • OutputPublish dated report page in Notion databaseNotionNotion

What it does

Rolls up a full week of distributed-trace data from Honeycomb into a written trend report. OpenAI describes how each service's latency and error rate moved across the week, calls out the worst regressions and best improvements, and the result is saved as a dated entry in a Notion database for an auditable history.

When to use it

Use it for weekly reliability reviews or engineering syncs where you want a durable, readable record of how the system trended, not just a live dashboard snapshot that disappears once the window scrolls.

How it works

  1. 1A weekly schedule fires (for example Monday morning).
  2. 2Honeycomb returns seven-day aggregates of latency percentiles and error rates grouped by service and day.
  3. 3OpenAI composes a structured narrative: week-over-week direction, standout regressions, notable improvements, and watch items.
  4. 4A Notion page is created in the reliability database, titled with the week range and populated with the report body.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HoneycombDistributed traces and queries.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.