Supabase Pro users can now send their Supabase logs to their own logging backend, enabling them to debug in the same place as the rest of their stack.

The Supabase Blog offers insights, tutorials, and updates on Supabase, an open-source alternative to Firebase for building scalable and real-time applications. Covering topics such as database management, authentication, and serverless functions, the blog provides resources for developers looking to leverage Supabase's features to build modern web and mobile apps. Developers can learn how to use Supabase to create secure, scalable, and performant applications that meet the needs of their users.

Supabase

Supabase has launched Log Drains for Pro tier users, allowing them to forward logs from all Supabase infrastructure layers (Postgres, Auth, Storage, Edge Functions, Realtime, API Gateway) to external logging backends. Supported destinations include Sentry, Grafana Loki, Datadog, AWS S3, Axiom, and any generic HTTP endpoint. Logs are batched (up to 250 per batch or every second) with optional Gzip compression. Pricing starts at $10 per drain per project plus $0.20 per million events and $0.09 per GB egress. The feature enables centralized observability across the full stack without context-switching between the Supabase console and existing monitoring tools.

Log Drains: Now available on Pro

What makes Supabase log drains different #

<p>And also Opentelemetry (OTLP) over HTTP</p>
