Supabase OpenTelemetry Integration

Supabase is an open-source Firebase alternative built on PostgreSQL. It bundles a managed Postgres database with authentication, auto-generated REST APIs, realtime subscriptions, file storage, and connection pooling.

This integration scrapes metrics from the Supabase Metrics API (Prometheus-compatible) using the OTel Collector's Prometheus receiver. Logs are forwarded through Supabase Log Drains into an Elastic Cloud managed endpoint. Elastic operates the endpoint for logs, so you do not need to install or run an OpenTelemetry Collector.

• Metrics (supabase.metrics.otel) — Infrastructure (CPU, memory, load, disk I/O, filesystem, network), PostgreSQL (size, connections, transactions, cache, WAL, replication, bgwriter, statements), Supavisor, PostgREST, Auth, Realtime, and Storage
• Logs (supabase.otel) — API Gateway, PostgreSQL, PostgREST, Edge Functions, Storage, Realtime, and connection pooling

Metrics are stored with native OTel schema — no field renaming or custom mapping is applied. Raw Prometheus metric names are preserved under the metrics.* namespace.

Once data starts flowing, the Supabase OpenTelemetry Assets package provides dashboards for infrastructure, PostgreSQL, application services, and service logs.

This integration requires a Supabase Pro, Team, or Enterprise plan. The Metrics API and Log Drains are not available on the Free tier.

The log drain path has been tested with Supabase Log Drains delivering OTLP logs to /inputs/supabase/_default_/v1/logs on the Elastic Cloud managed endpoint.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

1. Get your Supabase credentials:

   • Go to your Supabase dashboard → Settings → API
   • Copy the Project URL (e.g., abcdefghijkl.supabase.co)
   • Copy the service_role key (under "Project API keys")

2. Add the integration in Kibana:

   • Go to Management → Integrations → search for "Supabase"
   • Click Add Supabase
   • Fill in:
     • Targets: <your-project-ref>.supabase.co:443
     • Username: service_role
     • Service Role Key: paste your service_role JWT

Supabase logs reach Elasticsearch through a Supabase log drain that posts OTLP to an Elastic Cloud managed endpoint.

Setup has three parts, done in order:

1. Enable Supabase Log Drains.
2. Gather a managed endpoint URL and an API key from Elastic.
3. Create the log drain in Supabase.

Logs are available through Supabase Log Drains. Log drains require a Pro, Team, or Enterprise plan.

In Kibana, go to Add data → More → Supabase and copy the Supabase logs endpoint. The URL follows this pattern:

https://<managed-endpoint>/inputs/supabase/_default_/v1/logs
		

For example:

https://abc123.ingest.us-east-1.aws.elastic.cloud/inputs/supabase/_default_/v1/logs
		

Create an API key in the same view, or follow the Send data to Elastic Cloud quickstart. Supabase sends it as Authorization: ApiKey <your-api-key>.

1. Open Project Settings → Log Drains and create a drain.
2. Choose OpenTelemetry (OTLP) as the destination.
3. Set Endpoint to the Supabase logs endpoint URL, for example https://abc123.ingest.us-east-1.aws.elastic.cloud/inputs/supabase/_default_/v1/logs.
4. Set Protocol to http/protobuf and enable Gzip.
5. Add header Authorization: ApiKey <your-api-key>.
6. Save the drain.

In Discover:

• Metrics: data_stream.dataset: "supabase.metrics.otel"
• Logs: data_stream.dataset: "supabase.otel"

Supabase metrics are scraped by this integration. Log drain payloads are decoded by the Elastic Cloud managed endpoint and written to the data streams below. For log drain configuration on the Supabase side, see Log Drains. For managed endpoint behavior, see Managed inputs.

Metrics are scraped from the Supabase Metrics API endpoint:

GET https://<project-ref>.supabase.co/customer/v1/privileged/metrics
		

Authentication uses HTTP Basic Auth with service_role as the username and the service_role JWT as the password.

See the Supabase Metrics documentation for full details on available metrics.

All metrics are stored under the metrics.* field namespace with their original Prometheus names (e.g., metrics.node_load5, metrics.pg_stat_database_xact_commit_total).

The Logs data stream holds every service forwarded by the drain. Use the Service filter on the Service logs overview dashboard to focus on a single service.