Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
How TraceQL works
The TraceQL engine connects the Tempo API handler with the storage layer. The TraceQL engine:
- Parses incoming requests and extract flattened conditions the storage layer can work with
- Pulls spansets from the storage layer and revalidates that the query matches each span
- Returns the search response
The default Tempo search reviews the whole trace. TraceQL provides a method for formulating precise queries so you can zoom in to the data you need. Query results are returned faster because the queries limit what is searched.
For an indepth look at TraceQL, read the TraceQL: A first-of-its-kind query language to accelerate trace analysis in Tempo 2.0" blog post by Trevor Jones.
For examples of query syntax, refer to Construct a TraceQL query.
There’s supposed to be a video here, but for some reason there isn’t. Either we entered the id wrong (oops!), or Vimeo is down. If it’s the latter, we’d expect they’ll be back up and running soon. In the meantime, check out our blog!
Active development and limitations
TraceQL will be implemented in phases. The initial iteration of the TraceQL engine includes spanset selection and pipelines.
For more information about TraceQL’s design, refer to the TraceQL Concepts design proposal.
Future work
- Increase OTEL support: Events, Lists, ILS Scope, etc.
- Structural Queries
- Metrics
- Pipeline comparisons
Was this page helpful?
Related resources from Grafana Labs
