Repository navigation
feat(mcp-core): Surface intentional/unintentional tags in find_dropped_events - #1560
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was successfully deployed
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.
Summary
The
events-droppedendpoint tags each drop bucket asintentionalorunintentional(getsentry/sentry#127850, refined in #128138), butfind_dropped_eventswas stripping the field before the agent saw it. This surfaces it.tagsprovide extra information about drops:intentional— intended drops caused by user configuration (sampling, inbound filters,before_send).unintentional— drops the user did not intend (quota, abuse, invalid).The API-client schema already
.passthrough()estags, so only the tool layer needed the change.