fix(telemetry): tag sentry.org on api and event view - #1612
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
betegon
force-pushed
the
fix/telemetry-org-tag-api-event
branch
from
September 21, 2026 15:50
4f04d74 to
ca583c8
Compare
sentry api never goes through target resolve, so org usage is invisible in Discover. Parse the slug from the path. event view skips resolve-target on explicit/URL paths; tag after resolve. Co-authored-by: Cursor <cursoragent@cursor.com>
betegon
force-pushed
the
fix/telemetry-org-tag-api-event
branch
from
September 23, 2026 09:40
ca583c8 to
88196a3
Compare
betegon
marked this pull request as ready for review
September 23, 2026 11:22
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
sentry apinever goes through target resolve, sosentry.orgwas missing even when the slug was sitting in the URL. That undercounts orgs that live on raw API. Parseorganizations/{slug}/andprojects/{org}/{project}/from the path and tag.event viewhad the same hole on explicitorg/projectand event URLs — those paths skipresolve-target. Tag after resolve.schemais still untagged: it is local OpenAPI browse (auth: false), no org in the command. User identity is already set at telemetry init; org is not abuildCommanddefault because it is the resolved target, not "whoever is logged in".Test plan
packages/cli:pnpm exec vitest run test/commands/api.test.ts test/commands/event/view.test.tsMade with Cursor