chore(source-map-processing-errors): Emitting metric irrespective of …#115661
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
wedamija
approved these changes
May 15, 2026
Member
wedamija
left a comment
wedamija
left a comment
There was a problem hiding this comment.
Ahh, this explains what's going on here better, since these flags are only available on our org
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.
Move the
processing_errors.sourcemap_configuration.event_with_errorsmetric emission above theorganizations:sourcemap-issue-detectionfeature flag gate in_detect_for_config, so it fires for every org that ingests a JS event with a sourcemap processing error — not just internal Sentry orgsThe detector flow itself (
ensure_detector,process_detectors,DetectorStatewrites,IssueOccurrencecreation, refresh task updates) is still gated on the feature flag exactly as before, so no hidden issues get created for non‑enrolled orgs.