CHATBOTS

Slack Slash Command: Honeycomb Query to Linear Perf Ticket

A Slack slash command that runs a plain-English Honeycomb latency query, shows the p95 breakdown, and on confirmation files a Linear ticket pre-filled with the slow service.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerchat
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEngineer runs Honeycomb slash command in SlackSlack
  • ActionLLM translates question into a Honeycomb query specOpenAI
  • ActionRun query and post p95 breakdown with File-ticket actionHoneycomb
  • LogicWait for engineer confirmation before filing
  • OutputCreate pre-filled Linear perf ticket and reply with URLLinearLinear

What it does

Closes the gap between spotting a latency problem and tracking it. An engineer runs a slash command with a plain-English latency question; the bot builds and runs the Honeycomb query, replies with the p95 breakdown, and offers a button to file a Linear ticket pre-populated with the offending service, its p95, the time window, and a Honeycomb link.

When to use it

When latency findings get discussed in Slack and then forgotten because nobody opens a ticket. Use this to make filing a well-formed perf ticket a one-click step right from the query result.

How it works

  1. 1An engineer invokes the Slack slash command with a natural-language latency question.
  2. 2An LLM step translates it into a Honeycomb query spec — dataset, window, grouping, p95 metric.
  3. 3The bot runs the Honeycomb query and posts the p95 breakdown with a "File ticket" action.
  4. 4A branch waits for the engineer to confirm before any ticket is created.
  5. 5On confirmation the bot creates a Linear issue pre-filled with the slow service, p95 values, window, and Honeycomb link, then replies with the ticket URL.

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
    Connect LinearIssues, projects, cycles, triage.
  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.