link,[object Object]
ACQM Docs

Appearance

Monitoring ​

Purpose: What to track and how to observe system health. Audience: Owner, Developer Prerequisites: Deployed app; access to Supabase project and hosting.

App health

  • Uptime and error rate on hosting (Netlify/Vercel/S3 + CDN).
  • Client errors: capture console errors in production (optional Sentry or LogRocket).

Backend monitoring (Supabase)

  • Realtime usage: keep channels small. See src/hooks/useGlobalRealtimeNotifications.ts:24.
  • SQL errors: inspect postgresql logs in Supabase dashboard.
  • Function logs: Supabase Edge Functions logs per function (e.g., stripe-webhook).

Admin logs UI

  • Email logs dashboard: src/pages/admin/AdminLogs.tsx:28-45 queries email_logs and shows status.
  • Use it to check deliverability and error patterns.

Key dashboards

  • Authentication: sign-in error trends (GoTrue logs).
  • Database: slow queries and connection saturation.
  • Storage: object count and bandwidth.
  • Functions: error rate and cold starts.

Alerts

  • Stripe webhook failure rate > 1%.
  • Spike in failed logins or RLS denials.
  • Realtime disconnects increasing.

Analytics (optional)

  • Page views and funnels for explore → listing → offer.
  • Conversion to Starter/Pro.

Next steps

  • See docs/performance.md for tuning and caching.
  • See docs/features/notifications.md for notification channels and polling.