saved filters on sentry replay

[ant1m4tt3r]

Problem Statement

I would like to have saved filters in sentry replays.

Solution Brainstorm

A lot of our internal users of Sentry Replay here at my company are not tech people who find a little hard to get filters on Replay right, as they would have to understand a new query language basically.

If we as developers who better understand how to filter sessions based on events/identifications/extra tags could create and save filters for them it would be great!

It is not such a big deal TBH, mas it makes people lives easier and more pleasant to work with Replay.

In LogRocket for instance, you can create "Saved Segments" that are basically the same feature as I'm describing here, where you can pre-populate the filter query and share it in your org, so everyone else can use those same filters.

For instance, in a ecommerce page, I would like to have a saved filter that describes users that have made a purchase using PayPayl, so designers in my org can check if the experience looks good based on the users Replay sessions and usage patterns.

Product Area

Replays

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[ryan953]

@ant1m4tt3r Thanks for the feedback!

This has come up only a couple times since we launched replay early last year. The Issue stream has saved queries, but to be honest I think we haven't really committed to it because usage of the feature on Issues is a bit low.

I'll definitely surface this to our product manager and take another look at the numbers, especially with the 'click' queries that we've added the search terms can get really complex, so saved searches can make more sense now.

Also, if you (or anyone else reading) is using React you can checkout our bundler plugin which will make it possible to search for component names instead of the complex css selector stuff. It's much much easier to type out a query this way, in my opinion.

[ryan953]

cc @jas-kas

[ant1m4tt3r]

thanks for your time and consideration @ryan953!

i've checked the component filters for React, they're great, but don't solve the issue for us since the non-tech people i've mentioned seek to query sessions based on tags mainly.

let me know if i can be of any help or can further describe my ideas and usecases.