Dashboard Tour

Every project has its own dashboard at /<organization>/<project>. The sidebar groups the pages below. Press Cmd/Ctrl + K anywhere to open the command palette and jump to a page, project or action.

Overview

The landing page for a project answers "is anything wrong right now?":

• A one-line briefing built from what's true at the moment: open issues, escalating errors, checks that are down, missed crons.
• A triage queue of open issues, most severe first, then fastest-growing.
• The error pulse: event volume over the last 24 hours.
• Where it's breaking: a globe of where recent errors came from.
• Uptime bars for each check, cron status and the latest releases.

Issues

Events with the same fingerprint are grouped into one issue. See Error grouping. The list filters by status, level, environment and free text, and can be sorted by last seen, first seen or event count.

Triage from the keyboard:

Select several issues to resolve, ignore, assign or merge them in one step.

Issue page

Each issue reads like a case file:

• Title, status, level, first and last seen, the releases it appeared in, and snooze state.
• Stack trace, newest call first, de-minified when source maps are uploaded for the event's release. See Releases.
• Highlights and tag distribution: how recent events split across environment, release and every tag you send.
• Tags & context: everything the SDK attached to the event.
• All events, paged, with each event's own payload.
• People: assignee and participants, plus comments.
• What users said: linked user feedback.
• AI root-cause analysis, on demand. See below.

Actions: resolve, ignore, snooze, assign and comment.

AI root-cause analysis

Analyze with AI sends the issue's latest stack trace, tags, release and environment distribution, other stack shapes and linked user feedback to an OpenAI model after your project's PII scrubbing. You get a summary, the likely cause with its evidence, a suggested fix, a confidence level and what to check next. The result is saved on the issue for the whole team. Nothing is sent until someone clicks, and only owners, admins and developers can run it. Each plan includes a monthly allowance; see Error grouping.

Performance

Core Web Vitals from real visitors, per page, with a pass/fail verdict. See Performance & Web Vitals.

Logs

Structured logs with filters, a volume histogram and a live tail. See Logs.

User feedback

Notes users sent with captureFeedback, linked to their errors. See User feedback.

Uptime

HTTP and TCP checks. The list shows fleet availability, the last 90 probes per check and open incidents. Each check's page has current status, a 7-day hourly heatmap, incidents, SSL expiry, response times and the probe configuration. See Uptime.

Cron

Heartbeat monitors for scheduled jobs, with their ping URLs and last check-in. Ping URLs are visible to owners, admins and developers. See Cron heartbeats.

Queues

Laravel queue depth, job lifecycles, failures and unique locks, with optional queue control. See Queue monitoring.

Releases

Every release, newest first, with what it changed: new issues introduced, regressions, crash-free users while it was live, and events per hour compared with the previous release. See Releases.

Alerts

Rules on one side, channels on the other; hover either to trace a route. See Alerting.

Settings

Project settings:

• Install SDK: platform-specific snippets, pre-selected for your project's platform.
• Client keys: the project's DSNs.
• Upload tokens: secrets for CI (source maps, release markers, Laravel queue control).
• General, Privacy (PII scrubbing for events, logs and vitals) and Danger zone.

Organization settings cover members and roles, email domain auto-join, two-factor authentication, active sessions, email preferences and personal API tokens. Billing shows the plan and this month's usage. The public status page is configured from the Uptime page.