Skip to content

[pull] master from supabase:master #639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pull merged 3 commits into from
Feb 2, 2026
Merged

[pull] master from supabase:master #639

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0760733
Project create security section updates (#42021)
SaxonF Feb 2, 2026
f17f049
feat(log drains): add s3 form FE-2101 (#41031)
jordienr Feb 2, 2026
1706a67
Joshen/fe 2410 add default label to pg cron extension schema selector…
joshenlim Feb 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 30 additions & 11 deletions apps/docs/content/guides/telemetry/log-drains.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,13 @@ You can read about the initial announcement [here](/blog/log-drains) and vote fo

The following table lists the supported destinations and the required setup configuration:

| Destination | Transport Method | Configuration |
| --------------------- | ---------------- | ------------------------------------------------- |
| Generic HTTP endpoint | HTTP | URL <br /> HTTP Version <br/> Gzip <br /> Headers |
| DataDog | HTTP | API Key <br /> Region |
| Loki | HTTP | URL <br /> Headers |
| Sentry | HTTP | DSN |
| Destination | Transport Method | Configuration |
| --------------------- | ---------------- | -------------------------------------------------------------------------------------- |
| Generic HTTP endpoint | HTTP | URL <br /> HTTP Version <br/> Gzip <br /> Headers |
| Datadog | HTTP | API Key <br /> Region |
| Loki | HTTP | URL <br /> Headers |
| Sentry | HTTP | DSN |
| Amazon S3 | AWS SDK | S3 Bucket <br/> Region <br/> Access Key ID <br/> Secret Access Key <br/> Batch Timeout |

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.

Expand Down Expand Up @@ -136,13 +137,13 @@ Deno.serve(async (req) => {

</Accordion>

## DataDog logs
## Datadog logs

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.
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](https://app.datadoghq.com/organization-settings/api-keys) and the location of your DataDog site.
To setup Datadog log drain, generate a Datadog API key [here](https://app.datadoghq.com/organization-settings/api-keys) and the location of your Datadog site.

<Accordion
type="default"
Expand All @@ -153,9 +154,9 @@ To setup DataDog log drain, generate a DataDog API key [here](https://app.datado
id="walkthrough"
>

1. Generate API Key in [DataDog dashboard](https://app.datadoghq.com/organization-settings/api-keys)
1. Generate API Key in [Datadog dashboard](https://app.datadoghq.com/organization-settings/api-keys)
2. Create log drain in [Supabase dashboard](/dashboard/project/_/settings/log-drains)
3. Watch for events in the [DataDog Logs page](https://app.datadoghq.com/logs)
3. Watch for events in the [Datadog Logs page](https://app.datadoghq.com/logs)

</AccordionItem>

Expand Down Expand Up @@ -211,6 +212,24 @@ All fields from the log event are attached as attributes to the Sentry log, whic

If you are self-hosting Sentry, Sentry Logs are only supported in self-hosted version [25.9.0](https://github.com/getsentry/self-hosted/releases/tag/25.9.0) and later.

## Amazon S3

Logs are written to an existing S3 bucket that you own.

Required configuration when creating an S3 Log Drain:

- S3 Bucket: the name of an existing S3 bucket.
- Region: the AWS region where the bucket is located.
- Access Key ID: used for authentication.
- Secret Access Key: used for authentication.
- Batch Timeout (ms): maximum time to wait before flushing a batch. Recommended 2000–5000ms.

<Admonition type="note">

Ensure the AWS account tied to the Access Key ID has permissions to write to the specified S3 bucket.

</Admonition>

## Pricing

For a detailed breakdown of how charges are calculated, refer to [Manage Log Drain usage](/docs/guides/platform/manage-your-usage/log-drains).
Loading
Loading