Log Drains
Log drains will send all logs of the Supabase stack to one or more desired destinations. It is only available for customers on Team and Enterprise Plans.
Log drains is in Private Alpha, and is not available in the dashboard yet. Reach out to us to get log drains enabled for your project.
You can read about the initial announcement here.
Supported Destinations
The following table lists the supported destinations and the required setup configuration:
| Destination | Transport Method | Configuration |
|---|---|---|
| Generic HTTP endpoint | HTTP | URL HTTP Version Gzip Headers |
| Datadog | HTTP | API Key Region |
HTTP requests are batched with a max of 250 logs or 1 second intervals, whichever happens first. Logs are compressed via Gzip if the destination supports it.
Generic HTTP endpoint
Logs are sent as a POST request with a JSON body. Both HTTP/1 and HTTP/2 protocols are supported. Custom headers can optionally be configured for all requests.
Note that requests are unsigned.
Unsigned requests to HTTP endpoints are temporary and all requests will signed in the near future.
Datadog
Logs sent to Datadog have the name of the log source set on the service field of the event and the source set to Supabase. Logs are gzipped before they are sent to Datadog.
The payload message is a JSON string of the raw log event, prefixed with the event timestamp.
To setup Datadog log drain, generate a Datadog API key here and the location of your Datadog site.
If you are interested in other log drains, upvote them here