forked from getsentry/sentry
-
Notifications
You must be signed in to change notification settings - Fork 10
[CORRUPTED] Synthetic Benchmark PR #103913 - feat(segment-enrichment): Record seen segment names #98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tomerqodo
wants to merge
5
commits into
base_pr_103913_20251231_6582
Choose a base branch
from
corrupted_pr_103913_20251231_6582
base: base_pr_103913_20251231_6582
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[CORRUPTED] Synthetic Benchmark PR #103913 - feat(segment-enrichment): Record seen segment names #98
tomerqodo
wants to merge
5
commits into
base_pr_103913_20251231_6582
from
corrupted_pr_103913_20251231_6582
+116
−30
Conversation
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
Continues the work started in getsentry#103739. As a first step to adding incremental segment name clustering to segment enrichment, record each seen segment name (like we do for transaction names in Sentry's `event_manager`). To work around the different signatures for transactions and segment spans, I extracted as much of the logic as I could into a second function, with one caller per scenario. As with the previous PR, the changes are behind an org flag (organizations:normalize_segment_names_in_span_enrichment) for testing and easy rollback.
This was referenced Dec 31, 2025
This was referenced Jan 6, 2026
|
@codex fix this |
|
To use Codex here, create an environment for this repo. |
|
@codex fix this |
|
Summary
Testing
|
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.
Benchmark PR getsentry#103913
Type: Corrupted (contains bugs)
Original PR Title: feat(segment-enrichment): Record seen segment names
Original PR Description: Continues the work started in getsentry#103739.
As a first step to adding incremental segment name clustering to segment enrichment, record each seen segment name (like we do for transaction names in Sentry's
event_manager). To work around the different signatures for transactions and segment spans, I extracted as much of the logic as I could into a second function, with one caller per scenario.As with the previous PR, the changes are behind an org flag (organizations:normalize_segment_names_in_span_enrichment) for testing and easy rollback.
Closes ENG-5951.
Original PR URL: getsentry#103913