01 · Backend · Axiom
Convex backend health
Prod only, from Convex log streams. Call volume stacked by function (cache hits included); error rate and p95 latency count only calls that ran our code, since a cache hit can't fail and isn't work. Includes the three synthetic personas, which run around 01:00 UTC: Convex's run records carry no user, so they can't be filtered out yet. A rising error line is bad.
02 · Backend · Axiom
Latency & database bandwidth
Slowest prod functions by 95th-percentile execution time (cache hits left out), and the daily database read/write bytes across all deployments, dev included, because that is what Convex bills. Watch for a function whose bandwidth climbs without a matching call-volume rise.
03 · Backend · Axiom
Cron run matrix
Green where every scheduled run succeeded that day, red where any failed. This is the view that was missing during the 23:20 scanTradeReminders incident.
04 · Backend · Axiom
Ingest budget
Estimated Axiom ingest this month against the 500 GB free-tier cap, with an end-of-month projection. Estimated from event volume — Axiom doesn't expose true ingested bytes to a query token.
05 · Backend · Sentry
Backend exceptions
Un-redacted Convex exceptions from the dedicated honely-backend project. These carry the full server-side stack the client never sees.
06 · Mobile · Sentry
React Native app stability
Crash-free sessions and users, total error volume, the unresolved-issue queue. Events are flagged inverse — a rising line is bad.
07 · Web · Sentry
Marketing site stability
JavaScript + server errors on the marketing site. Spikes here typically correlate with a recent deploy — check the unresolved issues for the root cause.
08 · Web Vitals
Core Web Vitals · marketing site
75th-percentile values for Core Web Vitals captured on the marketing site in the last 7d. Bands follow Google's thresholds — green / amber / red colour the p75 directly.