-
-
Notifications
You must be signed in to change notification settings - Fork 58
Description
What problem could Sentry solve that it doesn't?
Problem
We’d like to monitor ANR (App Not Responding) rates for our Unity projects in the same way that native mobile SDKs expose ANR metrics such as anr_rate. Today, Unity’s ANR integration reports ANR events as Sentry issues, but there’s no clear way to derive or surface an ANR rate metric from those events at the SDK level. [Unity ANR docs]
Sentry already supports ANR-related rate metrics (for example, anr_rate) that can be used in dashboards and are being discussed for alerting and app hang rate functions. [App hang rate fn; Alerting on anr_rate] However, Unity-specific ANR detection currently focuses on event reporting and does not expose a first-class rate metric that we can reliably use for monitoring Unity ANR health over time.
What I’d like Sentry to solve
Provide an ANR rate metric for Unity (e.g. anr_rate or equivalent) that:
Can be queried in Discover and added to Dashboards, similar to existing anr_rate usage.
Can be used as a function in alert conditions (e.g. alert when Unity ANR rate exceeds a threshold).
Why this matters
ANRs are a critical quality signal for mobile games and apps built with Unity; we need a simple, standardized way to track Unity ANR rate over time, correlate it with releases, and set alerts when it regresses.
Today we can see Unity ANR issues, but we lack a clean, built-in rate metric comparable to what’s available for native Android ANRs and app hangs.
Having a first-class Unity ANR rate would make it easier to:
Track improvements when optimizing scene loading, main-thread blocking, etc.
Report ANR health to stakeholders using dashboards.
Automatically alert on regressions in Unity ANR behavior.

Metadata
Metadata
Assignees
Labels
Projects
Status
Status