Grafana Tempo: cost-efficient distributed tracing with TraceQL
Stand up Grafana Tempo on object storage, ingest OTLP/Jaeger/Zipkin and query with TraceQL — Helm deployment, multi-tenancy, service graphs
- What
- Stand up Grafana Tempo on object storage, ingest OTLP/Jaeger/Zipkin and query with TraceQL — Helm deployment, multi-tenancy, service graphs
- Cost
- Free
- Needs
- Docker (quick start) or Kubernetes (production) plus an object-storage bucket (S3/GCS/Azure); a Grafana stack with a Tempo datasource for querying; nothing else — no vendor accounts or keys required for the tracing backend itself
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @grafana's official skill for Grafana Tempo, the cost-efficient distributed-tracing backend that only needs object storage: stand it up locally with the official Docker Compose example (readiness and ingestion checks included), or deploy on Kubernetes with the `tempo-distributed` Helm chart (distributor, ingester, querier, query-frontend, compactor); ingest OTLP, Jaeger, Zipkin, OpenCensus and Kafka through the distributor → live-store → block-builder → object-storage write path; enable the metrics-generator for RED spanmetrics and service graphs; configure S3/GCS/Azure block storage and multi-tenant `X-Scope-OrgID`; write TraceQL across span/resource/event scopes with structural operators (`>>`, `<<`), `rate()` and `quantile_over_time` metrics; and wire the traces-to-logs/metrics/profiles datasource links for correlation. Includes debugging workflows for "no traces showing in Explore", querier/compactor sizing, and a full TraceQL operator cheat sheet. By @grafana, listed here with credit to its creator. Honest caveats: you provide the infrastructure — Docker/Kubernetes plus an object-storage bucket, and a Grafana stack with a Tempo datasource for querying; self-hosted, no vendor account required; Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: Docker (quick start) or Kubernetes (production) plus an object-storage bucket (S3/GCS/Azure); a Grafana stack with a Tempo datasource for querying; nothing else — no vendor accounts or keys required for the tracing backend itself Install "Grafana Tempo: cost-efficient distributed tracing with TraceQL" for me. It teaches an agent @grafana's official Tempo workflows: local Docker Compose stand-up with ingestion checks, Kubernetes deployment via the tempo-distributed Helm chart, OTLP/Jaeger/Zipkin ingestion, the distributor→block-builder→object-storage write path, metrics-generator for RED spanmetrics and service graphs, S3/GCS/Azure block storage, X-Scope-OrgID multi-tenancy, TraceQL queries (scopes, structural operators, rate()/quantile_over_time), querier/compactor sizing, and traces-to-logs/metrics/profiles correlation. Apache-2.0 licensed. Repository: https://github.com/grafana/skills/blob/main/skills/grafana-lgtm/tempo/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tempo". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. choose Docker quick start or the Helm production path; have the object-storage bucket ready; point my Grafana at the Tempo datasource). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.