Thema

#migration

Loots, Blogposts und verwandte Themen rund um diesen Tag. Folge dem Tag, damit passende Updates in deinem Orbit bleiben.

#migration

1Gezeigte Loots

8Gezeigte Artikel

8Verlinkte Nachbar-Tags

Anschluss-Themen

Wenn du tiefer einsteigen willst, helfen die benachbarten Tags beim Vergleichen und Querlesen.

Loot

Mehr aus diesem Thema

Alle Loots entdecken

Migrate Supabase logs.all queries before the September cutoff

#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