CHATBOTS

Scheduled Daily p95 Latency Digest to Microsoft Teams

Runs every morning to query Honeycomb for the prior day's p95 across key services, compares against the day before, and posts a ranked change digest to a Microsoft Teams channel.

CategoryChatbots
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule fires
  • ActionQuery Honeycomb for yesterday and prior-day p95 per serviceHoneycomb
  • LogicCompute day-over-day delta and rank by regression
  • LogicTag services that crossed the regression threshold
  • OutputPost ranked p95 digest to Microsoft Teams channelMicrosoft Teams

What it does

Delivers a proactive latency snapshot before anyone has to ask. On a daily schedule it queries Honeycomb for each tracked service's p95 over the last 24 hours, compares it to the previous day, ranks services by the size of the change, and posts a digest to Microsoft Teams so the team sees regressions at a glance.

When to use it

When you want a standing morning pulse on latency trends rather than waiting for an alert or a manual check. Good for platform teams that own multiple services and need a single shareable scorecard.

How it works

  1. 1A scheduled trigger fires each morning at a fixed time.
  2. 2The bot queries Honeycomb for yesterday's p95 per service, then for the prior day as a baseline.
  3. 3A logic step computes the day-over-day delta and percent change for each service.
  4. 4It ranks services by regression size and tags any that crossed a configured threshold.
  5. 5The bot posts a formatted digest — ranked deltas, current p95s, and Honeycomb links — to the Microsoft Teams channel.

Set it up

What you configure once, before turning it on.

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