Metrivo

Docs

Monitoring

Metrivo stores real application errors and warnings in Supabase so admins can review unresolved issues inside the product. The system works without any external vendor configuration.

What gets captured

  • Client rendering crashes through App Router error boundaries and browser `error` / `unhandledrejection` listeners.
  • Server and route-handler failures through the internal logger and Next.js `onRequestError` instrumentation hook.
  • Operational failures in tracker ingestion, payment webhooks, manual payment APIs, analytics endpoints, and revenue leak routes.

Privacy and masking

Before storage, Metrivo redacts passwords, tokens, API keys, cookies, authorization headers, webhook signatures, and other sensitive fields from messages, stacks, and metadata. Stack traces are only visible in the monitoring dashboard to authenticated admins.

Optional Sentry or GlitchTip forwarding

If you configure a Sentry-compatible DSN, Metrivo forwards each captured issue to that endpoint in addition to storing the internal row. GlitchTip works through the same DSN format.

SENTRY_DSN=
NEXT_PUBLIC_SENTRY_DSN=

Testing locally

  1. Open /app/monitoring as an owner or admin.
  2. Use Trigger Test Client Error to create a real browser-side error row.
  3. Use Trigger Test API Error to create a real server/API error row.
  4. Mark an issue resolved and confirm the unresolved count changes.
Back to documentation