---
name: "tempo-distributed-tracing-jaeger"
description: "Store and search massive distributed traces with sub-second retrieval using S3-backed Tempo."
metadata:
  author: "Grafana Labs"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "deploy grafana tempo"
  - "write traceql query"
  - "link traces to logs grafana"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Grafana Tempo High-Scale Distributed Tracing & S3 Storage

Deploys Grafana Tempo: configuring OTLP ingest, object storage backends (AWS S3, GCS), TraceQL query language, Jaeger / Zipkin protocol compatibility, and cross-linking traces to Loki logs and Prometheus metrics.

## When to Invoke
Invoke this skill whenever you need to:
- deploy grafana tempo
- write traceql query
- link traces to logs grafana

## Execution SOP & Rules
1. Configure tempo.yaml with storage: trace: backend: s3 and receiver: protocols: otlp: { grpc: {}, http: {} }.
2. Execute TraceQL queries in Grafana Explore: { status = error && duration > 2s }.
3. Configure derivedFields in Loki data source pointing to Tempo trace ID for one-click log-to-trace navigation.
4. Monitor Tempo ingestion rates and block compaction status via Tempo internal metrics.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.