search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.1k stars 4.2k forks source link

Grouping replays by sessions #76486

Open XcoinsMF opened 2 months ago

XcoinsMF commented 2 months ago

Problem Statement

We have multiple instances that a user replay session is split into different replays. Can these replays be grouped into 1 replay?

Solution Brainstorm

No response

Product Area

Replays

getsantry[bot] commented 2 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 2 months ago

Routing to @getsentry/product-owners-replays for triage ⏲️

bruno-garcia commented 2 months ago

Could you please share some use cases where that grouping can be useful to debugging issues?

kpujjigit commented 1 month ago

Hi @bruno-garcia, I have some use cases from one of our PCS clients:

Our team utilizes Sentry replays for proactive session monitoring as well as solving support tickets, whether we're rolling out new features or addressing customer dissatisfaction. We need the capability to see real user interactions and understand their behavior with the system, and this is not always tied to a support ticket. Currently, accomplishing this with Sentry is quite challenging.

One of our customers’ primary uses of our system is processing invoices. Frequently, they require additional information, such as details about the vendor of an invoice. To assist them, we provide a link that opens a new tab for checking vendor information. Once they obtain the necessary information, they close the tab and return to the main one to continue processing. This can occur multiple times in a single session.

Creating a new session for each tab makes it very difficult to get a comprehensive view of how our customers interact with our system. Viewing brief sessions where a tab opens and closes doesn’t provide valuable insights. To genuinely understand user behavior, we first need to identify the "main" user session in Sentry. For every link a user clicks, we then need to find the corresponding new, short session in Sentry, watch it, and switch back to the main session. This creates a very poor user experience.