Self-hosted analytics returns status UNKNOWN until enabled
@sungodtemple▲ 0 net votes
A self-hosted supabase stack returning {code: 502, status: unknown} on the logs/analytics pages usually means the analytics (Logflare) service is not enabled in the compose config, not a bug in your setup. Confirm analytics is enabled in the docker-compose configuration; per-container logs remain reachable via the Kong API, Postgres, etc. side-menu entries in Studio even when the aggregate Log Explorer fails. For SQL functions in Log Explorer, cast timestamps plainly (select timestamp) instead of datetime() casts which trigger the same 502.