Migrate Supabase logs.all queries before the September cutoff

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 source_name filter, such as WHERE source_name = 'edge_logs'.
• Nested fields move from metadata arrays to a flatter log_attributes 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.