Sentry Error Trend Dashboard

Generated 2026-05-10T00:35:20Z · project: not configured · lookback: 30 days ·

Configure Sentry token

To populate this dashboard, you need a Sentry auth token with org:read, project:read, and event:read scopes, plus the organization and project slugs.

1. Create a Sentry token

Visit sentry.io/settings/account/api/auth-tokens/ and create a token with scopes: org:read, project:read, event:read.

2. Save the token to macOS Keychain (local dev)

security add-generic-password   -s sentry-auth-token   -a "$USER"   -w "<your-token>"   -j "Sentry monitoring read-only (org:read, project:read, event:read)"   -U

3. Set GitHub Actions secrets (CI)

Find your org slug at sentry.io/organizations/ (it appears in the URL).
Find your project slug at sentry.io/organizations/<org>/projects/.

gh secret set SENTRY_AUTH_TOKEN --repo jasdsingh/personal-scripts
gh secret set SENTRY_ORG        --repo jasdsingh/personal-scripts --body "<org-slug>"
gh secret set SENTRY_PROJECT    --repo jasdsingh/personal-scripts --body "<project-slug>"

4. Re-run the dashboard workflow

After setting secrets: Actions → Sentry Error Dashboard Update → Run workflow.

Total events (30d)
n/a
All received events (org-level)
Unresolved issues shown
0
Top issues by event count
New issues (last 24 h)
0
First seen within 24 hours
Peak day
n/a
Highest event count day in window

Errors / Day (last 30 days)

No event data yet

Source: Sentry organization stats (stat=received). Counts all events received (includes repeated events on existing issues).

Top 10 Unresolved Issues by Frequency

Issue title Events Level Last seen First seen
No unresolved issues in window.

Performance: p95 / p99 by Transaction

Transactionp95p99
No performance transaction data. Performance monitoring requires a tracesSampleRate > 0 in the Sentry SDK config and at least one sampled transaction.

Requires tracesSampleRate > 0 in Sentry SDK config (lana/gmail/electron/sentry-init.js currently uses 0.1). Empty if no sampled transactions yet.

New Issues (Last 24 Hours)

New issues
0
First seen > 24h ago cutoff
Issues where firstSeen falls within the last 24 hours. These are error classes that have never been seen before — more actionable than repeat events on existing issues. Drill into them first; they indicate newly introduced regressions.

Issue Count by Level

error
0
warning
0
info
0
other
0

Breakdown of the top unresolved issues shown above, by Sentry severity level.

MAU Error Rate

Will populate post-launch. This panel will show: (users who experienced at least one error in the period) / (total MAU) as a percentage. Requires integrating Sentry user-impact data with product analytics once the app ships to real users.