tempo

Configure Grafana Tempo deployments for tracing scalability and cost-efficiency.

7|1|Updated Jul 12, 2026

Search Tags:#kubernetes #trace #opentelemetry #parquet #tempo #traceQL

Ready to run

npx skills add https://github.com/julianobarbosa/claude-code-skills --skill tempo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tempo
Source: https://github.com/julianobarbosa/claude-code-skills/tree/main/skills/tempo
Command: npx skills add https://github.com/julianobarbosa/claude-code-skills --skill tempo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill covers Grafana Tempo - a high-scale, multi-tenant tracing backend designed for OpenTelemetry, enabling efficient trace storage and TraceQL querying.

Core Features & Use Cases

TraceQL queries: Powerful trace-based querying with strong performance characteristics.
Object storage backed: Store traces in S3/GCS/Azure Blob with Parquet format.
Multi-tenant isolation: Built-in tenant isolation for multi-tenant tracing workloads.

Quick Start

Install Tempo with the distributed Helm chart and point to an object store; run a basic TraceQL query to locate traces by duration.

Frequently Asked Questions about tempo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a high-scale tracing backend for OpenTelemetry traces?▼

Grafana Tempo is a high-scale, multi-tenant tracing backend for OpenTelemetry. Deploy it on Kubernetes using the distributed Helm chart, configure an object store (S3, GCS, or Azure Blob) for Parquet-based trace storage, and point your OpenTelemetry collectors to Tempo's OTLP endpoint.

Can I query traces efficiently with TraceQL after storing them in Tempo?▼

Yes. TraceQL enables powerful trace-based queries with strong performance. Write queries to locate traces by duration, span attributes, or service names, then retrieve results from your object store backend.

Does Grafana Tempo support multi-tenant isolation for shared tracing deployments?▼

Yes. Tempo provides built-in multi-tenant isolation using X-Scope-OrgID headers, allowing you to isolate traces and queries by tenant within a single deployment on Kubernetes.

What object stores can I use with Tempo for trace storage?▼

Tempo stores traces in Parquet format across S3, Google Cloud Storage, or Azure Blob Storage, reducing storage costs while maintaining query performance on large-scale trace datasets.

How do I deploy Tempo across multiple cloud providers or on-premises environments?▼

Use the distributed Helm chart to deploy Tempo on Kubernetes. Configure the chart to point to your chosen object store backend—S3 for AWS, GCS for Google Cloud, or Azure Blob for Microsoft Azure—enabling multi-cloud flexibility.

What's the best way to troubleshoot traces and storage configuration issues in Tempo?▼

Use TraceQL queries to verify trace ingestion and storage, inspect Parquet blocks in your object store, check OTLP endpoint connectivity, and validate multi-tenant X-Scope-OrgID configuration across your Kubernetes deployment.