feat: add SendTracingContext option to httputil for OpenTelemetry tracing#546
Open
hweawer wants to merge 1 commit intofeat/tracing-writeback-executor-loggingfrom
Open
Conversation
hweawer
changed the title
| retry retryOptions | ||
| transport http.RoundTripper | ||
| ctx context.Context | ||
| tracingContext bool |
Collaborator
There was a problem hiding this comment.
why do we need an option for it? Why not turn it on by default?
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.
Summary
Add SendTracingContext option to httputil to enable OpenTelemetry distributed tracing support for HTTP client calls. This is foundational infrastructure for end-to-end trace propagation across Kraken services.
Motivation
Currently, Kraken has limited observability for debugging slow/failed blob uploads and downloads across distributed services. Adding distributed tracing will enable:
End-to-end visibility of blob upload/download flows
Correlation of logs across proxy → origin → backend
Debugging performance bottlenecks with precise timing data
Linking asynchronous operations (e.g., writeback tasks) to original requests
This PR provides the core HTTP infrastructure needed for trace propagation.