feat(replays): Record segment names that occur during replay#21851
Conversation
size-limit report 📦
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8f45b63. Configure here.
logaretm
left a comment
There was a problem hiding this comment.
Got some m/q comments in there. Also would be great to lock down the static spans (non-streaming) by asserting segmentNames in handleAfterSendEvent.test.ts. The afterSendEvent transaction path is writing names untested as far as I can tell.
|
@logaretm Thanks very much! I removed the coupling and added the missing test cases, if you wouldn't mind giving it another look. |

Record a new
segment_namesfield on replay events.This will be used in the product on the Transaction Summary page to fetch replays related to a particular named transaction.
This sidesteps our current issue under span streaming where Replay's
buffermode leads tosentry.replay.idattributes often pointing to missing Replays, which broke the assumption that a "query spans by segment name to get replay IDs, then query replays with those IDs" query flow will return a usable number of results.Closes REPLAY-937.