Docs for redact traces, faster read path, find traces arrays - #7144
Merged
knylander-grafana merged 6 commits intoMay 21, 2026
Conversation
knylander-grafana
requested review from
carles-grafana,
electron0zero,
ie-pham,
javiermolinar,
mapno,
mattdurham,
mdisibio,
oleg-kozlyuk-grafana,
ruslan-mikhailov,
stoewer,
yvrhdn and
zalegrala
as code owners
May 11, 2026 18:31
Contributor
There was a problem hiding this comment.
Pull request overview
Adds/updates Tempo documentation for three TraceQL/Tempo features that landed in earlier PRs (trace redaction via backend scheduler + tempo-cli, vParquet5 span-only fetch path for metrics, and array matching semantics in TraceQL).
Changes:
- Clarify TraceQL behavior when comparing attributes that contain arrays (including negated operators).
- Document
tempo-cli redactusage and how it interacts with the backend scheduler. - Document the experimental vParquet5 “faster read path” for TraceQL metrics queries and how to enable it.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/sources/tempo/traceql/construct-traceql-queries.md | Expands the “arrays” section to spell out =/=~ vs !=/!~ behavior on array-valued attributes. |
| docs/sources/tempo/operations/tempo_cli.md | Adds a new tempo-cli redact section describing usage, flags, output, and where to monitor scheduler job status. |
| docs/sources/tempo/metrics-from-traces/metrics-queries/_index.md | Adds an experimental note describing the vParquet5 span-only metrics read path and enablement knobs (hint + overrides). |
- Clarify faster read path requires explicit enablement (hint or override) - Remove unsafe_query_hints from override example (not required) - Note hint precedence is conditional on unsafe_query_hints being enabled - Fix backend-scheduler API docs anchor link
|
|
||
| In vParquet5, you can use an experimental span-only fetch layer to significantly improve performance for most metrics queries. This optimized read path processes individual spans instead of full traces, reducing latency and memory usage. | ||
|
|
||
| You must enable the faster read path explicitly using a query hint or a per-tenant override. Once enabled, it applies to metrics queries that don't require knowledge of the full trace structure. Queries using structural operators like `>>`, `<<`, `~`, `!>>`, `!<<`, or `!~` still use the standard fetch layer. |
zalegrala
approved these changes
May 21, 2026
Contributor
|
Looks good to me. |
3 tasks
knylander-grafana
added a commit
that referenced
this pull request
May 22, 2026
…arrays (#7208) * Docs for redact traces, faster read path, find traces with arrays (6832, 6359, 6353) * Address review comments on PR #7144 - Clarify faster read path requires explicit enablement (hint or override) - Remove unsafe_query_hints from override example (not required) - Note hint precedence is conditional on unsafe_query_hints being enabled - Fix backend-scheduler API docs anchor link * Apply suggestion from @knylander-grafana * Apply suggestion from @knylander-grafana * Apply suggestion from @knylander-grafana (cherry picked from commit 9f50627) Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com>
mattdurham
pushed a commit
to mattdurham/tempo
that referenced
this pull request
Jun 18, 2026
…#7144) * Docs for redact traces, faster read path, find traces with arrays (6832, 6359, 6353) * Address review comments on PR grafana#7144 - Clarify faster read path requires explicit enablement (hint or override) - Remove unsafe_query_hints from override example (not required) - Note hint precedence is conditional on unsafe_query_hints being enabled - Fix backend-scheduler API docs anchor link * Apply suggestion from @knylander-grafana * Apply suggestion from @knylander-grafana * Apply suggestion from @knylander-grafana
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add docs for PRs:
Which issue(s) this PR fixes:
Part of docs for release 3.0
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]