Conversation
Signed-off-by: 0YHR0 <97868579@qq.com>
✅ Deploy Preview for theagentrouter ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: 0YHR0 <97868579@qq.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
missBerg
added
design
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.
Description
The current MCP span combines the gateway's server role and its backend client roles, so fan-out backend latency and partial failures cannot be represented as independent operations.
Propose an opt-in SERVER span with per-backend CLIENT children, including unsampled propagation, independent request metadata ownership, JSON-RPC completion boundaries, and compatibility with current defaults. The design maps initialization, direct calls, aggregation, and notifications to concrete proxy integration points and specifies acceptance tests.
Related Issues/PRs (if applicable)
Design for #2562. This does not close the implementation issue.
Special notes for reviewers (if applicable)
Documentation only; no runtime topology changes. Please review the separate topology opt-in, request/dispatch trace handles, and matching-response completion semantics before implementation.
Developed with assistance from OpenAI Codex.