feat(admin): add global notification stats tab - #2847
Conversation
Store daily native push adoption and delivery counters in global_stats via a new native_notifications shard, and expose them in the admin dashboard. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (12)
Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_989404ec-0a28-45f1-9850-801f81063f1a) |
Merging this PR will not alter performance
Comparing Footnotes
|
There was a problem hiding this comment.
All reported issues were addressed across 12 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Fail the native_notifications shard when Cloudflare AE is unavailable instead of persisting false zeros, and align the admin tab with sibling isAdmin/defaultBack guards. Co-authored-by: Cursor <cursoragent@cursor.com>
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_523f240a-f9ef-42a0-82e6-31d36799e5ed) |
|



Summary (AI generated)
global_stats(apps using notifications, providers, campaigns, sent/received/opened/failed)native_notificationsglobal-stats shard that aggregates Postgres control-plane counts + Cloudflare Analytics Engine delivery eventsMotivation (AI generated)
Platform admins needed visibility into Capgo native notifications adoption and send volume. Delivery events live in Cloudflare AE and were not snapshotted for historical admin trends.
Business Impact (AI generated)
Makes notification product growth measurable in the admin console (apps onboarded, send volume, open/fail rates over time), supporting retention and packaging decisions.
Test Plan (AI generated)
buildGlobalNotificationStatsQueryday windowbun run supabase:db:reset/admin/dashboard/notifications/as platform admin and confirm KPI/charts loadglobal_statscolumns populate afternative_notificationsshard runsGenerated with AI
Made with Cursor