feat(runtime): add RuntimeTracer trait for task instrumentation#2467
Open
xanderbailey wants to merge 3 commits into
Open
feat(runtime): add RuntimeTracer trait for task instrumentation#2467xanderbailey wants to merge 3 commits into
RuntimeTracer trait for task instrumentation#2467xanderbailey wants to merge 3 commits into
Conversation
Allows callers to inject observability (tracing spans, metrics, etc.) into spawned tasks without modifying spawn sites. Inspired by DataFusion's JoinSetTracer but scoped per-Runtime rather than global, enabling different tracers for IO vs CPU handles.
Contributor
Author
|
@CTTY would be interested on your thoughts here? |
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
1 participant
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.
Allows callers to inject observability (tracing spans, metrics, etc.) into spawned tasks without modifying spawn sites. Inspired by DataFusion's JoinSetTracer but scoped per-Runtime rather than global, enabling different tracers for IO vs CPU handles.
Which issue does this PR close?
What changes are included in this PR?
Are these changes tested?