Overview
Every Insights tab, local range control, empty state, data source, and beginner gotcha — Frontend Overview, Traces, Web Vitals, Discover, Logs.
What is Insights?
Insights is the project’s stock performance and exploration surface: browser transaction throughput and duration, span traces with waterfalls, Core Web Vitals scoring, ad-hoc span aggregations, and console warn/error logs. It is not a custom dashboard builder — you switch among five fixed tabs.
It sits next to the marketing-style Dashboard (KPIs, pages, sources) and the Issues triage list. Insights answers “how is the product performing for real browsers?” rather than “how many visitors did we get?”
Route: /projects/:id/insights
Sidebar label: Insights
Top bar title: Insights
Tabs (local UI state — not in the URL)
Tabs are React state on the page. There is no ?tab= (or similar) query param.
| Tab label | Internal id | Guide |
|---|---|---|
| Frontend Overview | overview (default) | Frontend overview |
| Traces | traces | Traces |
| Web Vitals | web-vitals | Web vitals |
| Discover | discover | Discover |
| Logs | logs | Logs |
Gotcha — tabs are not deep-linkable. Refreshing the page always returns you to Frontend Overview. Bookmarking or sharing a URL will not restore Traces, Web Vitals, Discover, or Logs.
Shared sidebar filters vs Insights ranges
The sidebar Insights link can append the same shared analytics query string used elsewhere (range, offset, startDate, endDate, filters when present). The Insights page does not read those params for its widgets. Each tab keeps its own local range pills (and Discover/Logs keep their own filters). Changing Dashboard filters then clicking Insights does not drive these charts.
Each tab’s range default and options differ slightly — see the per-tab guides.
What data feeds Insights
| Surface | Primary API / data | What the SDK must send |
|---|---|---|
| Frontend Overview, Discover | POST /api/projects/:id/explore over the spans firehose | Performance / transaction spans (not just pageviews) |
| Traces | GET /api/projects/:id/traces (+ GET …/traces/:traceId for waterfall) | Page-load and related spans |
| Web Vitals | GET /api/projects/:id/web-vitals | Core Web Vitals samples |
| Issue Counts (overview card) | GET /api/projects/:id/insights/issue-counts | Runtime issues opened/resolved in range |
| Logs | GET /api/projects/:id/logs | Console warn/error logs captured to the logs store |
If you only installed pageview + replay capture, expect empty throughput/duration/assets/Discover until performance instrumentation is on. Issue Counts and Logs can still fill when those pipelines have data.
Insights is not…
- A widget composer or saved custom dashboard
- A replacement for Dashboard product analytics
- Deep-linked per-tab navigation (today)
Beginner workflow
- Confirm the SDK is sending performance / web vitals / console data (Developers → SDK).
- Open Frontend Overview with 14d (the product default — short windows are often empty on low traffic).
- Click a slow transaction → drill-down drawer → then open Traces for a sample waterfall.
- Check Web Vitals after a deploy; use Discover when you need a custom aggregation or group-by.
- Use Logs when you need warn/error console text across sessions, then Watch into a replay.