Querying OpenTelemetry metrics datasets in Honeycomb, whose rules differ from trace/event datasets: bare COUNT, RATE_SUM, RATE_AVG, RATE_MAX and CONCURRENCY are forbidden, temporal aggregation is automatic, and each metric has its own attributes. Use for gauges, counters, histograms and sums; temporal aggregation (RATE, INCREASE, SUMMARIZE, LAST); finding the metrics dataset, metric names and attributes; unexpected metrics results; infrastructure metrics (CPU, memory, disk I/O, network). Not for instrumenting metrics (use otel-instrumentation), event datasets with "metrics" in their name, or conceptual questions (use observability-fundamentals).
95
94%
Does it follow best practices?
Impact
99%
1.10xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Scanned
honeycombio/agent-skill
6bb0927
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.