What problem does it solve? Debugging production issues in a distributed TypeScript backend is slow when you cannot see how requests flow across routers, controllers, services, and repositories. This Skill provides the span attribute schema, TraceQL query patterns, and step-by-step workflows needed to find errors, slow operations, and broken request flows in Grafana Tempo. ## Core Features & Use Cases - Span Attribute Reference: Documents every attribute emitted by the auto-tracing utility (class.name, class.component, method.duration.ms, method.error.message, and more) so queries target real fields. - Ready-to-Use TraceQL Queries: Prebuilt queries for finding errors, filtering by component layer, detecting slow operations, and searching span inputs by content. - Debugging Workflows: Structured processes for investigating failed requests, performance regressions, and request flows, plus PromQL queries for spanmetrics dashboards. - Use Case: An API returns 500 on POST /appointments. Query { status = error && class.module = "appointment" }, inspect method.error.message and method.input.json, and identify the missing validation in the use case. ## Quick Start Ask the AI to find all error spans in the appointment module from Grafana Tempo and explain the root cause using the span attributes.
