Skip to content

fix(conventions): Preserve MCP transport and resource attributes - #6483

Draft
betegon wants to merge 2 commits into
masterfrom
bt/mcp-conventions-normalization
Draft

betegon wants to merge 2 commits into
masterfrom
bt/mcp-conventions-normalization

Conversation

@betegon

@betegon betegon commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Adopt sentry-conventions through 664f7b4 (getsentry/sentry-conventions#671) so MCP implementation names and resource URI schemes remain separate from OpenTelemetry network attributes. Previously mcp.transport=CustomHTTPTransport fabricated network.transport=CustomHTTPTransport, and a file resource scheme could prevent a real HTTP protocol from being backfilled.

Two regression tests exercise the real normalizer with and without network metadata. Both fail at the old conventions pin and pass after the update. The submodule upgrade also brings the intervening conventions changes documented in both changelogs.

Deploy before releasing SDK changes that emit implementation names without a known network transport, including getsentry/sentry-javascript#24506 and getsentry/sentry-python#7925.

AI-assisted change, reviewed and validated with the complete Rust workspace test/doc/format/clippy checks, Python library tests and Python lint/type checks. The full integration run has 989 passes, 59 skips and 12 upload failures caused by the local objectstore response missing session; all 12 also fail on the unchanged base commit with the same objectstore error.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant