Overview
Overview in the Overview area — route /app-overview.
Overview lives in the Overview area of the dashboard.
At a glance#
| Dashboard route | /app-overview |
| Area | Overview (overview) |
| Group | Ungrouped |
| Platforms | Available for every app platform. |
| Note | This entry points outside its area's usual /{area}/{slug} pattern. |
What it does#
This is the app's health summary — the one screen to open first each day. It reports the metrics a quality conversation actually turns on:
Crash-free sessions and crash-free users — the numbers the category commits to. On a web app the same measure is labelled error-free sessions, because "crash" is not a thing that happens to a page.
Error rate and network failures.
Problem sessions — sessions that contained a failure of any kind — with a per-day trend, so the page can answer "what changed?" rather than only "what is it now?".
Rage taps, as a frustration signal that no error report produces.
User reports, and how many are still unreviewed.
Replay coverage — how many problem sessions have a replay attached and how many do not, which tells you whether the next investigation will be watchable.
One headline performance number, chosen by platform: LCP p75 for web, app-start p95 for native.
Every tile that has somewhere to go is a link. The page is a starting point by design, not a destination.
When to use it#
Daily, and first. It is deliberately the only page that mixes signals from every area — stability, performance, frustration and feedback in one place — because on any given morning you do not yet know which of those is the problem.
Workflow#
Read crash-free first, against yesterday
The absolute figure matters less than the direction. A crash-free rate that dropped half a point overnight is a release regression.
Check the problem-sessions trend
It is the only time series here. A step change in it is dated, and a dated change has a cause you can go and find.
Look at replay coverage before you investigate
If coverage is low, raise it before the next incident rather than during it. You cannot retroactively record a session.
Clear unreviewed reports
They are the only signal on this page written by a person, and the only one that goes stale if ignored.
Permissions and prerequisites#
Read access to the app. Requires the SDK to be reporting sessions; individual tiles populate as their corresponding capability is enabled.
Limits and edge cases#
Tiles are resolved by platform, by absence. A web app is never shown an app-start tile and a native app is never shown Core Web Vitals — they are omitted rather than shown blank, so a missing tile is not a fault.
Every number here is an aggregate over a window. For "right now", use Live.
Trust depends on ingestion. A crash-free rate computed from a feed that dropped a third of its sessions is a statement about the feed. Check SDK Health before you quote any figure from this page externally.
Troubleshooting#
Crash-free is 100% and I do not believe it. Either genuinely no crashes in the window, or crash reporting is not arriving. SDK Health distinguishes those two, and this page cannot.
A tile is missing. Platform resolution, per above — or the capability behind it is not enabled in the SDK.
Where the data comes from#
Served by
App health
Dashboard