Skip to content
statusloopDocs
Guides

Monitor a Supabase app

HTTP checks, Edge Function health endpoints, and cron heartbeats for Supabase projects.

This guide shows patterns that work with statusloop today — no Supabase-specific integration required.

1. Monitor your API or REST endpoint

If your app exposes a health route (or Supabase REST is reachable):

  1. Monitors → Website / API
  2. URL: https://YOUR_PROJECT.supabase.co/rest/v1/ or your own API gateway health URL
  3. For authenticated checks, you cannot set custom headers in the monitor UI today — prefer a public /health route on your own domain that internally checks Supabase.

2. Edge Function health check

Deploy a Supabase Edge Function that returns { "ok": true }:

Deno.serve(() => new Response(JSON.stringify({ ok: true }), { status: 200 }));

Monitor: https://YOUR_PROJECT.supabase.co/functions/v1/health

3. Cron heartbeat (pg_cron or scheduled function)

When a nightly job or pg_cron task finishes, ping statusloop:

curl -fsS "https://app.statusloop.dev/ping/YOUR_SLUG"

Create a healthcheck with period matching your schedule and a 10+ minute grace period.

4. Status page

Link your API monitor and database-dependent components on a status page so customers see component-level status.

What statusloop does not do

  • No direct Supabase dashboard integration
  • No Postgres connection monitoring from statusloop's side (use HTTP/TCP to your API or agent on a VM if you self-host)
Was this helpful?

On this page