[OTEL] Wire RPC Telemetry propagation across rpc boundaries - #2874
Open
George Ng (GeorgeNgMsft) wants to merge 8 commits into
Open
[OTEL] Wire RPC Telemetry propagation across rpc boundaries#2874George Ng (GeorgeNgMsft) wants to merge 8 commits into
George Ng (GeorgeNgMsft) wants to merge 8 commits into
Conversation
George Ng (GeorgeNgMsft)
marked this pull request as ready for review
August 14, 2026 05:55
George Ng (GeorgeNgMsft)
enabled auto-merge
August 14, 2026 05:56
George Ng (GeorgeNgMsft)
disabled auto-merge
August 14, 2026 06:13
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.
This PR enables end-to-end OpenTelemetry trace continuity between the agent server and process-backed agents. RPC client and server spans now share the originating action trace while each process exports its own telemetry.
• Propagates bounded agent, action, session, and activation metadata.
• Excludes action parameters and RPC-internal context IDs.
• Covers success, failure, cancellation, and nested callbacks.
• Adds real subprocess integration coverage.
• Hardens secret filtering, browser compatibility, and subprocess startup handling.