Menu
Open source
Troubleshoot Tempo
This section helps with day zero operational issues that may come up when getting started with Tempo. The documents walk you through debugging each part of the ingestion and query pipeline to diagnose issues.
In addition, the Tempo runbook can help with remediating operational issues.
Sending traces
- Spans are being refused with “pusher failed to consume trace data”
- Is the Grafana Agent sending to the backend?
Querying
- Unable to find my traces in Tempo
- Error message “Too many jobs in the queue”
- Queries fail with 500 and “error using pageFinder”
- I can search traces, but there are no service name or span name values available
- Error message
response larger than the max (<number> vs <limit>)
Metrics Generator
Was this page helpful?
Related resources from Grafana Labs
Getting started with tracing and Grafana Tempo
In this webinar, we'll show you how to get started setting up Grafana Tempo, our open source, easy-to-use and high-volume distributed tracing backend.
Scaling your distributed tracing with Grafana Tempo
In this demo, we’ll show how Grafana Tempo allows you to scale tracing as far as possible with less operational cost and complexity than ever before.
TraceQL: a first-of-its-kind query language to accelerate trace analysis in Tempo 2.0
Grafana Tempo will take a big leap in the 2.0 release with TraceQL, a first-of-its-kind query language to help you find the exact trace you're looking for.