Self-hosted Logflare BigQuery backend possible?
self-hostedI have an existing self-hosted instance where Logflare is storing in the Supabase Postgres instance. Since there's no automatic cleanup, I figured it'd be better to ship the logs somewhere else.
I followed the docuentation here https://supabase.com/docs/reference/self-hosting-analytics/introduction#bigquery-backend-setup to a t and all I get are errors. I managed to get around the annoying startup issues of BigQuery rate limits by just restarting the analytics container a few times. The first issue is that Logflare never actually starts properly. The internal Logflare health check stays stuck at "coming_up" even though the container health check passes and logs are getting to BigQuery:
The second issues is now every tab in Logs gives me the following error:
Now, not every BigQuery table has logs in it. I'd expect that, but the tables that do have logs like the one for Kong, Postgres, Storage, etc do have a metadata column and data in them.
I followed the docuentation here https://supabase.com/docs/reference/self-hosting-analytics/introduction#bigquery-backend-setup to a t and all I get are errors. I managed to get around the annoying startup issues of BigQuery rate limits by just restarting the analytics container a few times. The first issue is that Logflare never actually starts properly. The internal Logflare health check stays stuck at "coming_up" even though the container health check passes and logs are getting to BigQuery:
The second issues is now every tab in Logs gives me the following error:
Now, not every BigQuery table has logs in it. I'd expect that, but the tables that do have logs like the one for Kong, Postgres, Storage, etc do have a metadata column and data in them.
