CHATBOTS

Slack Honeycomb Bot: Plain-English Latency Q&A

An on-demand Slack bot that turns a plain-English latency question into a Honeycomb trace query and replies in-thread with the p95 breakdown by service and route.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEngineer @-mentions bot with a latency question in SlackSlack
  • ActionLLM parses dataset, time window, operation, and metricOpenAI
  • ActionRun p95 query in Honeycomb grouped by service and routeHoneycomb
  • LogicRank rows and identify slowest contributors
  • OutputReply in Slack thread with p95 table and Honeycomb linkSlack

What it does

Lets any engineer ask a latency question in plain English from Slack — "what's the p95 on checkout in the last hour?" — and get back a real Honeycomb answer without writing a query. The bot parses intent, builds the corresponding Honeycomb query, runs it, and posts a p95 breakdown grouped by service and route, plus a deep link to the query in Honeycomb.

When to use it

When your team keeps pinging the one person who knows Honeycomb's query UI. Drop this in an engineering channel so anyone can self-serve latency answers during an incident or a routine perf check.

How it works

  1. 1An engineer @-mentions the bot in Slack with a natural-language latency question.
  2. 2An LLM step extracts the dataset, time window, target operation, and metric (defaulting to p95).
  3. 3The bot calls Honeycomb to run a query for the requested percentile, grouped by service.name and http.route.
  4. 4A formatting step turns the result rows into a ranked p95 table and computes the slowest contributors.
  5. 5The bot replies in the original Slack thread with the breakdown and a one-click link back to the query in Honeycomb.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect HoneycombDistributed traces and queries.
  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.