Structured workflows for investigating production issues in Honeycomb — the sequence of tool calls (context priming, broad query, BubbleUp, trace analysis, verification) and how to chain results between steps to reach root causes. Trigger phrases: "investigate production issue", "debug latency spike", "find root cause", "use BubbleUp", "analyze traces", "debug an outage", "why is my API slow", "errors are increasing", "health check", "SLO burning", or any request to investigate or debug production problems.
97
100%
Does it follow best practices?
Impact
87%
4.34xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Latency spike investigation with BubbleUp and hypothesis verification
Orient step executed
66%
100%
HEATMAP in initial query
0%
0%
get_service_map called
0%
100%
BubbleUp not skipped
0%
100%
BubbleUp 2D heatmap type
0%
100%
BubbleUp time range specified
0%
100%
BubbleUp value range specified
0%
100%
BubbleUp filters applied before trace
0%
100%
Verification WITH suspected cause
60%
100%
Control query WITHOUT suspected cause
40%
100%
create_board called
0%
50%
Board includes query run PKs
0%
25%
Error surge exception investigation workflow
Context priming
100%
100%
Schema discovery
0%
100%
BubbleUp not skipped
0%
100%
BubbleUp filter re-query
0%
100%
Separate exception event query
0%
100%
No span exception.message primary search
100%
100%
get_trace with show_events=true
0%
100%
Hypothesis verification query
55%
100%
create_board called
100%
100%
Board content: root cause summary
100%
100%
Board content: query PKs
28%
100%
Exception payload from event row
0%
87%
Deployment regression investigation with BubbleUp pagination
Orient step
0%
100%
Version comparison query
8%
100%
BubbleUp with group selection
0%
0%
BubbleUp pagination or max_columns
0%
100%
Multiple BubbleUp fields checked
0%
100%
BubbleUp not skipped
0%
100%
BubbleUp filters before trace
0%
50%
Explicit view_mode in get_trace
0%
100%
Hypothesis verified WITH filter
12%
100%
Control query WITHOUT filter
12%
87%
create_board called
37%
100%
Board includes query PKs
0%
0%
189553c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.