Monitoring
Issues and Performance in one shell: triage errors, then inspect browser transactions, traces, discover queries, and logs.
Monitoring is where you check whether the product is healthy. It has two modes in one shell: Issues for grouped errors, and Performance for frontend throughput, Core Web Vitals, traces, Discover, and logs.
Route
/projects/:id/monitoring/issues or /projects/:id/monitoring/performance
Older /projects/:id/issues and /projects/:id/insights URLs redirect into this
shell. The sidebar label is Issues for the issues mode; open Performance
with the segmented control at the top of Monitoring.
Modes
| Mode | Segment | Job |
|---|---|---|
| Issues | issues | Grouped runtime, repo, behavioral, and visual problems. See Issues. |
| Performance | performance | Browser transactions, Web Vitals on the overview, plus explore panels. See Performance. |
Shared Monitoring range pills: 24h · 7d · 14d (default) · 30d.
Optional env= filters by SDK environment.
Explore panels (Performance)
From Performance overview you can open explore views with ?explore=:
| Query | Surface |
|---|---|
| (none) | Frontend overview (default) |
explore=traces | Traces |
explore=discover | Discover |
explore=logs | Logs |
These are URL-backed. Bookmark or share the query string to return to the same
panel. ← Back to overview clears explore.
There is no separate Web Vitals tab. Core Web Vitals render on the Performance overview next to transaction cards.
Related
Filters
Every shipped filter, date, saved segment, scoped replay, refresh, live-session, and player-adjacent control on the Replays route.
Performance overview
Monitoring → Performance: browser transaction throughput and duration, Core Web Vitals on the overview, and links into traces, Discover, and logs.