Analytics issues on self host
All analytics collections are empty besides Edge Functions and Cron which displays error . I couldn't find anything on google to fix this issue
11 Replies
@pitic try clearing Supabase project logs cache or re deploying your containers; if the issue persists, it may be a backend bug contact Supabase support with the error JSON and project ID
Hey. I even deleted all the volumes, images etc., ran supabase start to pull everything back again and the issue persisted
502 on edge functions and cron jobs is a known issue https://github.com/supabase/supabase/issues/33549
Previously logs for other services were present, with this update those are gone as well
Are you using supabase cli or docker-compose?
Supabase cli
You can keep a track of the issue. If you want to see the edge function logs for debugging, you can look at the container logs
I am more interested in the other logs right now
You can take a look at them as they are being stored in other db in the container but they will be raw logs.
json formatted
would docker compose with a lower version of analytics help?
I remember other logs working previously, edge functions and cron logs issue was known
you can try previous release of supabase cli, if you're more comfortable with cli
On a local dev thread Silentworks says the latest CLI is broken for logs and to go to a earlier version. Not sure if that applies to self-hosting too.
Yes there is an issue with the Studio itself which was fixed around two weeks ago but the release might have not made it to the self-hosted setup as yet. https://github.com/supabase/supabase/issues/37218