Is self hosting possible and feasible?
Supabase Logs: open-source logging server
11–20 of 68 posts
Re: Supabase Logs: open-source logging server
#12Is self hosting possible and feasible?
Yes, the docs are here: https://supabase.com/docs/reference/self-hosting-analytics/i...
One caveat: the only backend-store supported right now BigQuery. We will be releasing support for Clickhouse and Postgres in the coming months, we just couldn't fit it into this Launch Week
Re: Supabase Logs: open-source logging server
#13hey hn, supabase ceo here this one is a long-time coming and it's a continuation of our acquisition of Logflare[0]. Since the acquisition we've be open-source-ing the server, which you can find here: https://github.com/Logflare/logflare Logflare handles about 1.5 billion log-events everyday on supabase. It's built with Elixir and has no problems with that workload. This is really just the start of the Logflare update…
Sentry is open-source.
Re: Supabase Logs: open-source logging server
#14hey hn, supabase ceo here this one is a long-time coming and it's a continuation of our acquisition of Logflare[0]. Since the acquisition we've be open-source-ing the server, which you can find here: https://github.com/Logflare/logflare Logflare handles about 1.5 billion log-events everyday on supabase. It's built with Elixir and has no problems with that workload. This is really just the start of the Logflare update…
thank you thank you. the longer i spend as a dev the more i have infinite appreciation for better logging.
this is asking a lot but could we get a breakdown as to what you think are relevant decision factors for choice of logging server? (eg vs logstash/kibana, splunk and i guess people DIY with clickhouse but we can effectively ignore that)
Re: Supabase Logs: open-source logging server
#15I weep a bit every time I see a new Supabase capability knowing I'm stuck on Firebase.
Firebase uses Google Cloud Logging. Taking a quick look at the blog post here, Google Cloud Logging already seems to support everything it describes. Is there something in it that makes it a better solution in some way than what Google is already providing? (Note that Supabase Logs appears to rely on Google BigQuery so you'll be running on Google either way.)
not for long:
> Logflare currently supports a BigQuery backend. We plan to add support for other analytics-optimized databases, like Clickhouse. We will also support pushing data to other web services, making Logflare a good fit for any data pipeline. > > This will benefit the Supabase CLI: once Postgres support is available, Logflare will be able to integrate seamlessly, without the BigQuery requirement.
Re: Supabase Logs: open-source logging server
#16https://github.com/Logflare/logflare/tree/staging > Simply provide your BigQuery credentials and we stream logs into your BigQuery table while automatically managing the schema I didn't know BigQuery was capable of accepting streaming log data - in my mental model of the world it was the kind of database that you update using the occasional batch job, not from a streaming source of data. Looks like that's the tableda…
It's pretty awesome & very cost effective! When I was at Twilio we streamed logstash/fluentd (forget which) -> kinesis -> BigQuery and it worked great - certainly better than the days we were trying to manage ES ourselves
is kinesis in the middle for more durability/being able to handle spikes? when and how does one make that sort of decision to insert kinesis into things? (esp since you were gonna get the data from aws -> gcp so you dont save anything staying within aws anyway)
Re: Supabase Logs: open-source logging server
#17hey hn, supabase ceo here this one is a long-time coming and it's a continuation of our acquisition of Logflare[0]. Since the acquisition we've be open-source-ing the server, which you can find here: https://github.com/Logflare/logflare Logflare handles about 1.5 billion log-events everyday on supabase. It's built with Elixir and has no problems with that workload. This is really just the start of the Logflare update…
Sentry is open-source.
Simply drawing a comparison with that comment, so that readers know the direction of the product.
I'll leave my comment above unedited, so that your comment makes sense - but perhaps I shouldn't have said "alternative", and simply left it a "Over time Logflare will function very much like Sentry."
Re: Supabase Logs: open-source logging server
#18> Logflare was available under a BSL license prior to joining Supabase. We’ve since changed the license to Apache 2.0, aligning it with our open source philosophy. I wish more companies were like this! (note, the vector.dev link is broken)
thanks for spotting that, fixed here: https://github.com/supabase/supabase/pull/13594
Re: Supabase Logs: open-source logging server
#19hey hn, supabase ceo here this one is a long-time coming and it's a continuation of our acquisition of Logflare[0]. Since the acquisition we've be open-source-ing the server, which you can find here: https://github.com/Logflare/logflare Logflare handles about 1.5 billion log-events everyday on supabase. It's built with Elixir and has no problems with that workload. This is really just the start of the Logflare update…
Seems that a lot of Supabase's project ls written in Elixir, which is not a very popular choice.
What is the reason behind choosing Elixir?
Re: Supabase Logs: open-source logging server
#20Exists a pino transport?