Disparity between Issue and Replay breadcrumbs

[leeandher]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Set up some custom breadcrumbs in the SDK
2. Create an issue with an associated Replay
3. Check out the breadcrumbs on issue details
4. Compare with that on the replay.

Expected Result

The breadcrumbs contain identical, if not extremely similar data. They're both titled breadcrumbs after all, and look fairly consistent with one another.

Actual Result

Neither tell the whole story.

On issues:

• SDK crumbs (sentry_sdk.add_breadcrumb()) appear
• Console statements (if they get picked up by the SDK) will appear as breadcrumbs
• A few mouse clicks/ page loads may appear, though it usually depends on the nature of the event

On replays:

• SDK crumbs do not appear
• Console statements have their own tab, so they don't appear in the breadcrumbs
• Much more user interaction is shown, page clicks, navigations, usually far before the event.

Some goals:

• I don't think it'd make sense for the issue details page to contain all the Replay crumbs for user navigation minutes before the event actually takes place, but at least just before the event, I'd expect them to match
• Each pull from their own data set right now which makes them diverge, it'd be ideal if they pulled from one data set and filtered to what users might wanna see in each UI

Another option:

• If we don't want them to match, or want this data appearing identical (e.g. adding console/custom breadcrumbs to replays, adding more user interaction to issue details), then we could rename that tab on the replays side to create a clearer distinction. We can't reliably update the name on the issues side since they are called out in SDK function names, so it'd create some confusion.

Product Area

Replays

Link

No response

DSN

No response

Version

No response