Sentry Error Trend Dashboard

Generated 2026-07-08T05:15:59Z · project: lana · lookback: 30 days ·

Total events (30d)

n/a

All received events (org-level)

Unresolved issues shown

Top issues by event count

New issues (last 24 h)

First seen within 24 hours

Peak day

n/a

Highest event count day in window

Errors / Day (last 30 days)

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

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.

New Issues (Last 24 Hours)

New issues

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

warning

info

other

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.