Conversation
… span and transaction Removes all references to "service entry span" from the codebase: - In code: renamed to "segment span" (types, variables, functions, API referrers) - In UI: renamed to "transaction" (user-facing labels and text) - Renamed files: serviceEntrySpansTable.tsx -> segmentSpansTable.tsx, useServiceEntrySpansQuery.tsx -> useSegmentSpansQuery.tsx - Updated API referrer strings: service-entry-spans -> segment-spans - Simplified conditional logic that became redundant after unifying terminology Co-authored-by: Claude (Anthropic) <claude@anthropic.com>
github-actions
bot
added
Scope: Frontend
Contributor
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
Backend changes for referrer renaming will be handled in a separate PR. Co-authored-by: Claude <noreply@anthropic.com>
Member
Author
|
Updated to move BE changes to their own PR. |
narsaynorath
approved these changes
Feb 17, 2026
mjq
added a commit
that referenced
this pull request
Feb 17, 2026
## Summary Renames Snuba referrer constants from "service entry spans" to "segment spans" to align with updated product terminology. This is a backend-only change that updates the referrer constant names used in Snuba queries. The frontend changes are in a separate PR. ## Changes - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE` → `API_INSIGHTS_SEGMENT_SPANS_TABLE` - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE_WITH_CATEGORY` → `API_INSIGHTS_SEGMENT_SPANS_TABLE_WITH_CATEGORY` - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE_COUNT` → `API_INSIGHTS_SEGMENT_SPANS_TABLE_COUNT` ## Related Frontend changes: #108355 Co-authored-by: Claude <noreply@anthropic.com>
mjq
removed
the
Scope: Backend
mchen-sentry
pushed a commit
that referenced
this pull request
Feb 24, 2026
… span and transaction (#108355) ## Summary This PR refactors terminology across the performance monitoring UI, replacing "service entry span" with "segment span" in code and "transaction" in user-facing strings. The UI might also eventually start calling these things segments or segment spans too, but that will be a global change if done and not just in this new EAP version of the transaction summary. ## Changes **Terminology Updates:** - Code identifiers: `ServiceEntrySpans` → `SegmentSpans` - TypeScript types: `ServiceEntrySpansRow` → `SegmentSpansRow` - User-facing UI: "Service Entry Spans" → "Transactions" **File Renames:** - `serviceEntrySpansTable.tsx` → `segmentSpansTable.tsx` - `useServiceEntrySpansQuery.tsx` → `useSegmentSpansQuery.tsx` **Simplifications:** - Removed `shouldUseOTelFriendlyUI` parameter and conditional logic - Simplified breadcrumb and empty state messages to always use "transaction" - Cleaned up unused imports and parameters ## Related Backend referrer changes: #108358 --------- Co-authored-by: Claude (Anthropic) <claude@anthropic.com> Co-authored-by: Claude <noreply@anthropic.com>
mchen-sentry
pushed a commit
that referenced
this pull request
Feb 24, 2026
## Summary Renames Snuba referrer constants from "service entry spans" to "segment spans" to align with updated product terminology. This is a backend-only change that updates the referrer constant names used in Snuba queries. The frontend changes are in a separate PR. ## Changes - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE` → `API_INSIGHTS_SEGMENT_SPANS_TABLE` - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE_WITH_CATEGORY` → `API_INSIGHTS_SEGMENT_SPANS_TABLE_WITH_CATEGORY` - `API_INSIGHTS_SERVICE_ENTRY_SPANS_TABLE_COUNT` → `API_INSIGHTS_SEGMENT_SPANS_TABLE_COUNT` ## Related Frontend changes: #108355 Co-authored-by: Claude <noreply@anthropic.com>
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.
Summary
This PR refactors terminology across the performance monitoring UI, replacing "service entry span" with "segment span" in code and "transaction" in user-facing strings.
The UI might also eventually start calling these things segments or segment spans too, but that will be a global change if done and not just in this new EAP version of the transaction summary.
Changes
Terminology Updates:
ServiceEntrySpans→SegmentSpansServiceEntrySpansRow→SegmentSpansRowFile Renames:
serviceEntrySpansTable.tsx→segmentSpansTable.tsxuseServiceEntrySpansQuery.tsx→useSegmentSpansQuery.tsxSimplifications:
shouldUseOTelFriendlyUIparameter and conditional logicRelated
Backend referrer changes: #108358