Inbound filter for session replay
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
I'm interested in rolling out session replay from the mobile sdks, but I'm a little hesitant because replay is so much more expensive (unit-wise) than most of the other capabilities. I control my own replay sampling rate from a configuration server, but I'd be more comfortable if I had a means to stop ingesting replays from the Sentry web console also. It'd probably be nice to have a granular filter for those, but for now I'd be happy with a on/off switch.
Solution Brainstorm
I think I'd like to see a switch for session replay in .../settings/projects/{proj}/filters. I looked around a bit for something that might satisfy this, but didn't find it anywhere else. Feel free to point me towards it if that already exists.
Product Area
Ingestion and Filtering
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the project filter settings at .../settings/projects/{proj}/filters and tracing how session replay ingestion is currently filtered. Confirm how an on/off switch should affect replay intake, then verify that the web-console setting controls ingestion as expected without requiring a granular filter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100