ENGINEERING

Compile a weekly slow-query latency digest to Confluence and Slack

Each week, aggregates the top latency outliers across services from Honeycomb, ranks them by total time spent.

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires Monday morning
  • ActionQuery Honeycomb for top slow operations over 7 daysHoneycomb
  • LogicRank by cumulative cost; compute week-over-week deltas
  • ActionCreate or update Confluence perf digest pageConfluenceConfluence
  • OutputPost top-5 offenders and regressions to SlackSlack

What it does

Once a week it rolls up the most expensive slow spans across all monitored services from Honeycomb, ranks them by cumulative time cost and trend versus last week, and writes a clean Confluence page that anchors the team's perf review.

When to use it

When you run a recurring performance review and want a consistent, data-backed agenda instead of ad-hoc dashboard screenshots. Use it to track whether last week's offenders actually improved and to surface new regressions.

How it works

  1. 1A weekly schedule fires Monday morning.
  2. 2Query Honeycomb for the top slow operations per service over the last 7 days, with p50/p99 and total time.
  3. 3A logic step ranks offenders by cumulative latency cost and computes week-over-week deltas.
  4. 4Create or update a Confluence page with a ranked table, each row linking to a Honeycomb query.
  5. 5Post a Slack summary of the top 5 offenders and the biggest regressions with the Confluence link for the review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HoneycombDistributed traces and queries.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.