otel-queries

# OTel Queries Use this skill to inspect gh-aw OpenTelemetry/OTLP data and answer telemetry questions without re-deriving trace fields, backend filters, and diagnostics. ## When To Use Use this skill for requests such as: - analyze OTEL or OTLP data - inspect traces in Grafana, Tempo, Sentry, Honeycomb, or Datadog - explain why a workflow or agent run is slow or failing - compare run phases, error clusters, or span attributes - identify the best observability or performance improvement - close the loop from telemetry into code or workflow changes Do not use this skill for instrumentation-only tasks that do not require reading telemetry. For pure emit-side work, start with the existing OTLP code and docs. ## Primary Goal Reduce a broad telemetry task to one tight loop: 1. Find the cheapest trustworthy telemetry source. 2. Run a small fixed set of common queries. 3. Confirm one concrete bottleneck, missing attribute, or broken correlation path. 4. Answer the user's telemetry question directly. 5. Recommend or implement a follow-on optimization only when the evidence supports it. ## Telemetry Sources In Priority Order Prefer sources in this order unless the user says otherwise: 1. Local artifacts or mirrors already in the workspace. 2. `/tmp/gh-aw/otel.jsonl` for gh-aw spans. 3. Live OTLP backend data through an MCP server or supported tool — Copilot CLI spans are exported directly to the configured OTLP backend (no local file mirror) and must be queried there, filter...