Topic

#supabase

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#supabase
#developer-tools#api#auth#bigquery#cdc#envoy#kong#migration
Loot

More from this topic

Explore all loot
Migrate Supabase logs.all queries before the September cutoff

Migrate Supabase logs.all queries before the September cutoff

0
#supabase#api+3
Supabase is removing the old logs.all Management API endpoint on September 23, 2026; this resource points developers to the new ClickHouse-backed logs endpoint and migration notes. Supabase published a migration note for teams that query the Management API logs.all analytics endpoint directly. The old endpoint is scheduled for removal on September 23, 2026. Use this as a bookmark if you have scripts, internal dashboards, observability jobs, MCP tooling, or agent workflows that call .../analytics/endpoints/logs.all. What changes: Endpoint path changes from analytics/endpoints/logs.all to analytics/endpoints/logs. Queries must use ClickHouse SQL. Logs now come through a unified logs table. Source-specific queries need a sourcename filter, such as WHERE sourcename = 'edgelogs'. Nested fields move from metadata arrays to a flatter logattributes map. This is not a dashboard change. Supabase says the dashboard Logs Explorer is not affected. The risk is custom code that calls the Management API endpoint directly and assumes the old table-per-source structure. Check your codebase for logs.all, analytics/endpoints/logs.all, and old metadata unnesting patterns, then convert the queries against Supabase's new logs endpoint before the cutoff.
Free
Review open
0
Open loot
Stream Supabase Postgres Changes to BigQuery with Supabase Pipelines

Stream Supabase Postgres Changes to BigQuery with Supabase Pipelines

0
#supabase#postgres+3
Supabase Pipelines is a managed CDC service for sending Supabase Postgres changes to BigQuery in near real time. Supabase Pipelines is now in public alpha for paid Supabase plans. It gives teams a managed change-data-capture path from Supabase Postgres to analytics destinations, starting with BigQuery, without running a separate Debezium, Kafka, or custom replication stack. Use it when production Postgres is doing double duty as both app database and analytics source. Pipelines reads from Postgres logical replication, performs an initial copy of selected tables, and then streams inserts, updates, deletes, and truncates with at-least-once delivery. What to evaluate before depending on it: Availability is public alpha, so behavior and supported destinations can change. BigQuery is the current managed destination; Supabase says more destinations are planned. It runs on paid Supabase plans, not self-hosted Supabase. Row filters, selected tables, column subsets, partitioned tables, schema-change handling, and dashboard monitoring are part of the published setup surface. Best fit: teams already on Supabase that want operational data in BigQuery for analytics, reporting, enrichment, or downstream AI workflows while keeping heavy analytical reads away from the application database.
Free
Review open
0
Open loot
Blog

Related reads

Browse blog
Tools & Apps

Supabase self-hosted installs move from Kong to Envoy in August

Supabase will make Envoy the default API gateway for self-hosted Docker installs in the week of August 9, 2026, with compatibility paths for…

Tools & Apps

Fix self-hosted Supabase auth routes before SAML breaks

Supabase is changing the default self-hosted API_EXTERNAL_URL to include /auth/v1 in the next self-hosted release, with SAML SSO route chang…