getsentry / sentry

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

Issue alerts based on releases don't work well for mobile #74327

Open gpeal opened 1 month ago

gpeal commented 1 month ago

Problem Statement

The alert rules only let you filter based on the latest release in a given environment. However, mobile release processes tend to have multiple in flight at the same time. It would be nice if there was an option to have an alert rule that only filtered for releases < a certain age (like 2 weeks or 3 weeks). Filtering on the latest release only makes the feature unusable for mobile because a release gets created but doesn't roll out for a week.

Solution Brainstorm

  1. Allow a rule to be the most recent X releases
  2. Allow a rule to be the releases <X age
  3. Allow a rule to be based on releases that >X% of sessions Something else along those lines

Product Area

Alerts

getsantry[bot] commented 1 month ago

Auto-routing to @getsentry/product-owners-alerts for triage ⏲️

getsantry[bot] commented 1 month ago

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

rachrwang commented 1 month ago

@gpeal - thank you for filing this idea. To clarify where you would find this most useful - is that issue alerts, metric alerts, or possibly both?

gpeal commented 1 month ago

@rachrwang Issue alerts although I imagine this would be useful anywhere something like this is sued.

rachrwang commented 1 month ago

Thanks! This is an area we're interested in exploring, though there aren't exact timelines or plans that I can communicate at this moment.