---
title: "Log Drains: Now available on Pro"
description: "Supabase has launched Log Drains for its Pro tier, allowing users to send Supabase logs to their own logging backend and investigate them alongside the rest of their stack. The feature addresses the separation between Supabase logs and external observability tools by exporting events from Postgres, API Gateway, Auth, Storage, Edge Functions, and Realtime. Logs are sent over HTTP in batches of up to 250 entries or every second, whichever comes first, with Gzip compression when supported by the destination. Supported destinations include Sentry, Grafana Loki, Datadog, AWS S3, Axiom, and generic HTTP endpoints; users configure drains in the dashboard and can create multiple drains, with pricing of $60 per drain per project, $0.20 per million events, and $0.09 per GB of egress."
---

# Log Drains: Now available on Pro

[Supabase](https://yomu.fyi/company/supabase) · steven\_eubank · Mar 5, 2026

**Type:** Announcement

## Summary

Supabase has launched Log Drains for its Pro tier, allowing users to send Supabase logs to their own logging backend and investigate them alongside the rest of their stack. The feature addresses the separation between Supabase logs and external observability tools by exporting events from Postgres, API Gateway, Auth, Storage, Edge Functions, and Realtime. Logs are sent over HTTP in batches of up to 250 entries or every second, whichever comes first, with Gzip compression when supported by the destination. Supported destinations include Sentry, Grafana Loki, Datadog, AWS S3, Axiom, and generic HTTP endpoints; users configure drains in the dashboard and can create multiple drains, with pricing of $60 per drain per project, $0.20 per million events, and $0.09 per GB of egress.

## Context

Supabase logs previously remained in the Supabase console instead of the external logging and observability tools teams used for application debugging. This forced engineers to switch between dashboards and correlate timestamps across application, database, authentication, storage, and other infrastructure events during incidents.

## Approach / What changed

Log Drains send Supabase logs over HTTP to supported destinations including Sentry, Grafana Loki, Datadog, AWS S3, Axiom, or a generic HTTP endpoint. Users create drains from Project Settings in the Supabase Dashboard, can configure multiple destinations, and receive batches of up to 250 logs or a flush every second, with Gzip compression when supported.

## Takeaways

- Supabase exports logs from Postgres, API Gateway, Auth, Storage, Edge Functions, and Realtime, providing visibility beyond application-level events.
- Logs are sent in batches of up to 250 entries or flushed every second, whichever comes first; Gzip compression is used when the destination supports it.
- Pricing is $60 per drain per project, $0.20 per million events, and $0.09 per GB of egress, and multiple drains can send logs to different destinations simultaneously.

**Tags:** [AWS](https://yomu.fyi/topic/aws), [Monitoring](https://yomu.fyi/topic/monitoring), [Observability](https://yomu.fyi/topic/observability), [Postgres](https://yomu.fyi/topic/postgres)

- Source: [Supabase](https://supabase.com/blog/log-drains-now-available-on-pro)
- Source URL: https://supabase.com/blog/log-drains-now-available-on-pro
- Ingested by Yomu: 2026-08-29T04:01:00.457Z

[Read original post](https://supabase.com/blog/log-drains-now-available-on-pro)