Supabase
Send your Supabase project's logs to FlareLog with a log drain, with no SDK and no code change. Database errors, Edge Function output and failed requests arrive as FlareLog issues.
Supabase offers log drains on the Pro plan and above, and bills each drain separately. See Supabase's drain pricing.
One click
- In your FlareLog project, open Settings → Connect → Supabase.
- Select Connect Supabase, choose your organization on Supabase's consent screen and approve access.
- Pick your Supabase projects.
FlareLog creates an API key and adds a log drain named FlareLog to each project. You'll see it under Project Settings → Log Drains in Supabase. FlareLog revokes its Supabase access when it's done. Connecting again updates the existing drain instead of adding another.
By hand
In Supabase, open Project Settings → Log Drains and add a Custom Endpoint drain.
Use this URL, with Gzip on:
https://flarelog.dev/api/v1/drains/supabaseAdd these headers:
Authorization:Bearer <your FlareLog API key>. Create an ingest key in your project's Settings → API keys.X-Supabase-Project(optional): a name for the project. FlareLog shows it as the source of the logs.
What FlareLog keeps
| Service | Kept | Skipped |
|---|---|---|
| Postgres | ERROR, FATAL and PANIC as errors, WARNING as warnings | LOG, INFO, NOTICE and DEBUG (checkpoints, connections, cron runs) |
| Edge Functions | Console output and uncaught exceptions, with the stack | Boot and shutdown events |
| API gateway and Edge Function requests | Requests that returned 5xx, as METHOD /path returned 503 | Successful requests |
| Auth | Warnings and errors | Routine requests |
| PostgREST, connection pooler, Storage, Realtime | Lines that report an error | Everything else |
Skipped logs don't count toward your plan. FlareLog doesn't store the visitor IP addresses, locations, request headers, user agents, JWT details or email addresses that Supabase includes.
Disconnecting
In your FlareLog project, open Settings → Connect → Supabase and select Disconnect Supabase. You sign in to Supabase again, pick the organization, and choose which projects to disconnect. FlareLog deletes their FlareLog drain, so Supabase stops sending logs and stops billing the drain. Once no drain in the organization uses it, FlareLog deletes its API key, then revokes its Supabase access. Logs FlareLog already has are kept.
To do it by hand, remove the FlareLog drain under Project Settings → Log Drains in Supabase, then delete the key in your FlareLog project's Settings → API keys.
Using the SDK too
The drain covers what Supabase runs. For errors in your frontend or your own server, and for AI call tracking, add the FlareLog SDK to your app as well. See Lovable for apps built there.