fix(dashboards): Use span.op for MCP pre-built dashboard filters#115540
Merged
gggritso merged 1 commit intoMay 14, 2026
Merged
Conversation
The MCP pre-built dashboards filtered spans on `span.name:mcp.server`, but a recent Relay change corrected the `name` of MCP spans, so the filter no longer matches and the dashboards stopped loading data. Switch to `span.op:mcp.server`, which is the stable defining attribute for these spans. Fixes DAIN-1673 Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.51% |
nikkikapadia
approved these changes
May 14, 2026
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
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.
getsentry/relay#5961 correctly (but unexpectedly) changed the
nameattribute for MCP spans, which caused our pre-built dashboards to stop loading data, because thespan.name:mcp.serverfilter is no longer valid. Instead, we need to usespan.opwhich is less semantic but is actually correct!I also have a migration to repair existing widgets, there are only ~100: #115543
References DAIN-1673.