Skip to content

[Epic] Rage Click Issue and Alerting #60826

@bruno-garcia

Description

@bruno-garcia

We’ve heard from many customers that they want to be alerted on UX issues. We set out to do this but with the first iterations the detection logic was far from ideal. After a few iterations we believe we’re close.

Sentry is able to show you replays that have Dead and Rage Clicks. These are the first two replay UX issues we've implemented detection logic for, here some ideas for future ones.

Additionally, Sentry can show you selectors across all pages/replays that cause Dead and Rage clicks

Initial intent

Automatically subscribe to alerts on Rage Click issues. Possibly (if needed) threshold might be used in the default alert (e.g., min 30 clicks on N selector) in order to find the right signal-to-noise ratio.

Additional background

We started in the quest of detecting issues through Replay data (#45664) earlier with the goal of alerting on those. Our first iterations was on Dead click alerting and turned out to be quite noisy (#48259 (comment)). We added Rage click support on top of it, which means: Rage clicking on a Dead element.

The signal here is much stronger, and with aggregation on selector, we believe we're closer to building something we can alert on.

Ultimately this is still a research project. We'll consider alerting on selectors, if too noisy, a metric alert could be the next best thing.
Finally, if the signal-to-noise here isn't good, we might have alerting as an opt-in or simply drop alerting altogether.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions