Generated 2026-05-10T00:35:20Z · project: not configured · lookback: 30 days ·
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.
Visit sentry.io/settings/account/api/auth-tokens/ and create a token with scopes: org:read, project:read, event:read.
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
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>"
After setting secrets: Actions → Sentry Error Dashboard Update → Run workflow.
Source: Sentry organization stats (stat=received). Counts all events received (includes repeated events on existing issues).
| Issue title | Events | Level | Last seen | First seen |
|---|---|---|---|---|
| No unresolved issues in window. | ||||
| Transaction | p95 | p99 |
|---|---|---|
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.
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.
Breakdown of the top unresolved issues shown above, by Sentry severity level.