honeycomb-tracing
Installation
SKILL.md
Honeycomb Tracing
Produce an inspectable waterfall tied to the actual run or CI attempt, explain which intervals dominate elapsed time, and identify the smallest useful next experiment. Respect diagnosis-only requests; tracing does not itself authorize replaying tasks, changing credentials, or deploying instrumentation.
Choose the data path
| Question | Start here |
|---|---|
| Why is a task slow before, during, or after model execution? | Application workflow below; runtime setup if spans are absent |
| Why does an issue page load slowly? | Request spans plus browser timing, described below |
| Which CI jobs or test files delay the whole suite? | CI profiling |
| Where should a new span go? | Instrumentation guidance below and Observability contract |
Repository-relative paths and commands assume the checkout root. The maintained
contracts are doc/observability.md and doc/ci-profiling.md; recheck them and
the owning code when a deployed version differs.