Open souredoutlook opened 1 year ago
Assigning to @getsentry/support for routing, due by (yyz). ⏲️
Routing to @getsentry/replay for triage, due by (yyz). ⏲️
@evanpurkhiser will your graph screenshot widget will cover/can be ported for this use case easily? [I'm not implying this is a priority, just connecting the dots since Evan demo'd something similar for graphs very recently]
leaving this here https://github.com/rrweb-io/rrvideo
Embedded Replays might allow authenticated Sentry users to view the playback outside of Sentry in whatever tool is used to manage project work.
@souredoutlook seems like retention might be an issue for this here? People might want to be able to go back to a ticket a few months later and still view the replay. Being able to export as a video they can store externally seems like the most likely way to make this possible.
Hello @souredoutlook, I'm also interested in the outcome of this issue. Many users, including those on platforms like LogRocket (me) and PostHog, benefit from the ability to export session data for long-term storage or later restoration. It would be extremely useful if Sentry could integrate a feature that allows exporting replays directly to a cloud service like Google Cloud Storage, S3 Buckets. This would enable us to save replays for longer periods and restore them to Sentry when needed, providing flexibility in managing and archiving session data.
Thanks for describing your use case. Could you share in more detail what types of problems does this workflow help you with? Replays live in Sentry for 3 months, that's for bugs that happen where the replay is helpful but the issue isn't high priority? Woundn't a similar replay come in eventually if the issue is still going on?
hey @bruno-garcia. Thanks for your reply! Indeed, the recurring bugs can typically be captured by Sentry's 3-month retention. However, the need for exporting session replays extends beyond bug tracking. In business-critical situations, especially where user actions have legal or financial implications, the ability to review a user's session even after a long time can be invaluable. For example, consider a user's interaction with a tax filing application. If discrepancies are found in their tax submission, they might query this several months or even a year later. Having the ability to retrieve and review the session replay could provide crucial insights into user behavior, help rectify any user errors, or defend the application's functionality.
By allowing us to export and archive session data, we'd be empowered to support long-term audits, compliance requirements, and customer service inquiries.
Thanks for sharing your use case! That makes sense. We're working on a service that can render the replay and allow us to get screenshots/video as well as accessibility issues. Once that's live we'll be unblocked to add this and a round of prioritization will happen
Problem Statement
Customers want to be able to add Replays to work items in places like Jira, Asana, Linear etc.
The request is usually framed like so:
Solution Brainstorm
Embedded Replays might allow authenticated Sentry users to view the playback outside of Sentry in whatever tool is used to manage project work.
See linked Support Request: https://sentry.zendesk.com/agent/tickets/80723
Additional use case from @vinayman (issue)