Send Supabase Logs to SigNoz

Supabase Log Drains can forward logs from the Supabase stack to any OpenTelemetry Protocol (OTLP) compatible endpoint. This guide shows how to send those logs to SigNoz using Supabase's built-in OTLP drain.

Prerequisites

A Supabase project on the Pro, Team, or Enterprise plan. Log Drains are not available on the Free plan.
Access to Project Settings -> Log Drains in the Supabase dashboard
A SigNoz endpoint for logs and, for SigNoz Cloud, an ingestion key

Step 1: Open Log Drains in Supabase

Open your project in the Supabase dashboard.
Go to Project Settings -> Log Drains.
Click Add destination.

Step 2: Select the OTLP destination

On the Log Drains screen, click OpenTelemetry Protocol (OTLP).

Supabase Log Drains screen with OpenTelemetry Protocol (OTLP) available as a destination — *Supabase Log Drains screen*

Step 3: Configure the destination

Create a new destination with the following values:

Name: Choose a name such as signoz-logs
Type: OpenTelemetry Protocol (OTLP)
OTLP Endpoint: https://ingest.<region>.signoz.cloud/v1/logs
Protocol: HTTP/Protobuf
Gzip Compression: Enabled
Custom Header: signoz-ingestion-key: <your-ingestion-key>

Verify these values:

<region>: Your SigNoz Cloud region
<your-ingestion-key>: Your SigNoz ingestion key

Most steps are identical. For self-hosted setups, update the endpoint and remove the ingestion key header as shown in Cloud → Self-Hosted.

Supabase Log Drains support only HTTP/Protobuf. For self-hosted setups, use your OTLP/HTTP endpoint instead of the SigNoz Cloud ingest URL. OTLP/HTTP endpoints commonly listen on port 4318. For the standard OTLP/HTTP endpoint format, see OpenTelemetry Collector OTLP HTTP exporter docs.

Supabase sends OTLP requests with the application/x-protobuf content type automatically. No additional configuration is needed on the SigNoz side as long as you use the /v1/logs endpoint.

Supabase OTLP destination form configured to send logs to SigNoz — *Supabase OTLP destination configuration*

Step 4: Save the destination

Click Save destination. Supabase will start forwarding new log events to SigNoz.

Supabase batches outbound requests for log drains. According to the official docs, OTLP drains send up to 250 log events per request or flush once per second, whichever happens first.

Validate

After saving the destination, verify that logs are flowing into SigNoz:

Navigate to Logs > Explorer in your SigNoz dashboard.
Generate fresh activity in your Supabase project (API requests, auth flows, Postgres queries, etc.).
Within about a minute, new Supabase log entries should appear.

Expected behavior: You should see fresh log entries coming from Supabase services. The exact fields depend on the originating product, such as Auth, API/Edge, Postgres, Realtime, Storage, or Edge Functions.

You can click on a particular log entry in the Logs view to open the expanded log details.

Troubleshooting

Logs not appearing in SigNoz

Symptom: No Supabase logs are visible in SigNoz after saving the drain.

Things to investigate:

Incorrect OTLP endpoint
- The endpoint must be the full OTLP logs URL and typically ends with /v1/logs
- For SigNoz Cloud, check the correct region-specific ingest URL here: SigNoz Ingestion Docs
Wrong protocol selected
- Supabase OTLP drains currently support only HTTP/Protobuf
- This issue typically applies to self-hosted SigNoz setups with a custom endpoint, not SigNoz Cloud
- Reopen the destination and confirm the protocol is set correctly
Missing or invalid authentication header
- Verify the signoz-ingestion-key header value
- If you are using self-hosted SigNoz, remove the ingestion key header unless your setup requires custom auth
No recent Supabase events
- Log drains forward new events, not historical logs
- Generate fresh traffic in the products you want to observe
OTLP endpoint is not publicly reachable
- Verify your SigNoz endpoint accepts OTLP log traffic from external services
- If you are sending to a self-hosted collector behind a proxy or firewall, confirm it is reachable over HTTPS

Next steps

Monitor Supabase metrics: Add the Supabase metrics integration
Use the Supabase dashboard: Import the Supabase Monitoring Dashboard
Query logs: Use the Logs Explorer to search and filter Supabase logs
Create alerts: Set up log-based alerts for repeated errors or unusual log patterns

Limitations

Plan availability: Supabase Log Drains are available only on Pro, Team, and Enterprise plans
OTLP protocol support: Supabase OTLP drains currently support only HTTP/Protobuf
Batched delivery: Logs are delivered in batches rather than one event per request