feat(api): Add MCP referrer to search_events API calls - #1118
Merged
Conversation
Set referrer=api.mcp.search-events on Discover and EAP /events/ requests so Sentry can attribute search_events traffic. The validate endpoint does not accept referrer, so it is omitted there. Co-Authored-By: Claude Sonnet 4 <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Member
|
at some point we should figure out how to avoid doing this, since our customers wont do it for us, and we already have api application attribution capabililty on the backend |
Member
Author
|
Makes sense, I'll revisit this later to see if i can improve it |
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.
Set referrer=api.mcp.search-events on Discover and EAP /events/ requests so Sentry can attribute search_events traffic.