production-investigation

Name: production-investigation
Availability: InStock
Author: Honeycomb

Automate production issue investigation in Honeycomb with structured workflows.

20|7|Updated Feb 7, 2026

Search Tags:#debugging #root cause analysis #observability #incident response #honeycomb #production issues

Ready to run

npx skills add https://github.com/honeycombio/agent-skill --skill production-investigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: production-investigation
Source: https://github.com/honeycombio/agent-skill/tree/main/honeycomb/skills/production-investigation
Command: npx skills add https://github.com/honeycombio/agent-skill --skill production-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides structured workflows to systematically investigate and debug production issues in Honeycomb, guiding users from initial alerts to root cause identification.

Core Features & Use Cases

Guided Investigation: Follows a step-by-step process (Orient, Characterize, BubbleUp, Drill Into Traces, Verify, Record) to diagnose problems.
Root Cause Analysis: Leverages Honeycomb's BubbleUp feature to find differentiators and get_trace to analyze individual request flows.
Use Case: When a "latency spike" alert fires, this Skill will guide you through running broad queries, using BubbleUp to identify the cause (e.g., a specific deployment version), and then drilling into traces to confirm the bottleneck.

Quick Start

Use the production-investigation skill to debug a latency spike.

Frequently Asked Questions about production-investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug production issues in Honeycomb?▼

You can debug production issues in Honeycomb using a structured workflow that guides you from initial alerts to root cause identification via context gathering, broad querying, BubbleUp analysis, and trace examination.

What is the best way to investigate a latency spike or error surge?▼

The best way to investigate latency spikes or error surges is following a step-by-step process: orient, characterize, use BubbleUp to find differentiators, drill into traces, verify, and record the findings.

How does BubbleUp analysis work for root cause analysis?▼

BubbleUp analysis works for root cause analysis by finding differentiators in your query data, allowing you to identify specific causes of production issues such as a particular deployment version causing a latency spike.

Can I use this workflow to debug deployment regressions and dependency failures?▼

Yes, you can use this workflow to debug deployment regressions and dependency failures, as it provides structured investigation workflows specifically addressing these production issue scenarios.

Do I need any dependencies to automate incident response with this process?▼

No dependencies are required to automate incident response with this process, as it orchestrates Honeycomb tool calls internally to investigate production issues without external dependencies.

What steps are involved in examining individual request flows during an incident?▼

Examining individual request flows involves using the get_trace functionality to analyze traces after identifying differentiators with BubbleUp, allowing you to confirm the specific bottleneck causing the production issue.