> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supabase

> Add an OpenTelemetry log drain in the Supabase dashboard pointed at your Sazabi intake URL to forward Postgres, Auth, and Edge Function logs.

[All Supabase integration capabilities](https://docs.sazabi.com/catalogs/integrations/supabase)

## About

Stream your Supabase Postgres, Auth, and Edge Function logs into Sazabi. Set up an OpenTelemetry (OTLP) log drain in Supabase that points at Sazabi, and Supabase sends your project's logs to Sazabi automatically. There is no agent or sidecar to deploy.

> [!WARNING]
>
> Log Drains require a Supabase **Pro**, **Team**, or **Enterprise** plan. The Free plan does not include Log Drains. You can upgrade in the Supabase dashboard under **Project Settings > Billing**.

## Prerequisites

* A Supabase project on the **Pro**, **Team**, or **Enterprise** plan.
* Your Sazabi intake URL (shown above).

## Set up in the dashboard

**Step 1**

### Open the log drain form

In the [Supabase dashboard](https://supabase.com/dashboard), open the project whose logs you want to forward, then open **Project Settings > Log Drains** and click **Add destination**.

**Step 2**

### Set name and type

Fill in the **Name** and **Description** fields:

* Name: `Sazabi`
* Description: `Forward Supabase logs to Sazabi for observability and AI analysis.`

Set **Type** to **OpenTelemetry Protocol (OTLP)**.

**Step 3**

### Set the OTLP endpoint

Paste your Sazabi intake URL (shown above) into the **OTLP Endpoint** field.

**Step 4**

### Set protocol and compression

* **Protocol**: `HTTP/Protobuf`
* **Gzip Compression**: Enabled

**Step 5**

### Save

Save the log drain. Supabase begins sending logs to Sazabi immediately.

## Set up with the CLI

You can also register the Supabase log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create supabase --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Run a query against your Supabase project or hit your project's API to generate log activity. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm logs from the **Supabase** source appear. Logs typically arrive within a few minutes of the activity.

## Troubleshooting

**Log Drains option not visible** — Log Drains appear only on Pro, Team, and Enterprise plans. If the option is missing from **Project Settings**, check your current plan under **Project Settings > Billing** and upgrade if needed.

**No logs after saving the drain** — Confirm you selected **HTTP/Protobuf** as the protocol and that **Gzip Compression** is enabled. Also check that the OTLP endpoint URL in the Supabase drain settings exactly matches your Sazabi intake URL.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [Instrument](https://docs.sazabi.com/guides/instrument.md)
>
> Learn how to send data to Sazabi.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.