[querier] Support external mode for traceID lookups#6185
Merged
electron0zero merged 9 commits intomainfrom Jan 13, 2026
Merged
Conversation
This PR adds a new `external` mode to the querier. In this mode, an HTTP
request is sent to an external endpoint to fetch trace contents in
addition to the normal ingester + block storages.
The external API is expected to support an API matching Tempo's
TraceIDV2 API. `/api/v2/traces/{traceID}?start=<start>&end=<end>`. This
endpoint should respond with an OTLP proto encoded trace.
This can be used to augment tempo's internal traceID lookup with
additional data that may not be ingested to tempo directly.
Logiraptor
requested review from
carles-grafana,
electron0zero,
ie-pham,
javiermolinar,
joe-elliott,
knylander-grafana,
mapno,
mattdurham,
mdisibio,
oleg-kozlyuk-grafana,
ruslan-mikhailov,
stoewer,
yvrhdn and
zalegrala
as code owners
Contributor
|
💻 Deploy preview available ([querier] Support external mode for traceIDv2): |
Logiraptor
changed the title
| # Tempo's TraceIDV2 API (/api/v2/traces/{traceID}). | ||
| external: | ||
| # Enable querying an external endpoint for trace data. | ||
| [enabled: <bool> | default = false] |
Member
There was a problem hiding this comment.
do we need the enabled flag in here as well? I see that we have external_enabled config under the frontend section as well?
Contributor
Author
There was a problem hiding this comment.
It's not strictly necessary. Is this what you had in mind? 7d1c116
Co-authored-by: Suraj Nath <9503187+electron0zero@users.noreply.github.com>
Contributor
|
💻 Deploy preview deleted ([querier] Support external mode for traceID lookups). |
electron0zero
approved these changes
Jan 13, 2026
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
2 participants
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.
What this PR does:
This PR adds a new
externalmode to the querier. In this mode, an HTTP request is sent to an external endpoint to fetch trace contents in addition to the normal ingester + block storages.The external API is expected to support an API matching Tempo's TraceIDV2 API.
/api/v2/traces/{traceID}?start=<start>&end=<end>. This endpoint should respond with an OTLP proto encoded trace.This can be used to augment tempo's internal traceID lookup with additional data that may not be ingested to tempo directly.
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]