Live data from Hacker News

Supabase Logs: open-source logging server

supabase.com

51–60 of 68 posts

Re: Supabase Logs: open-source logging server

#51
post #46

Earlier quoted context omitted.

Cool :) We would need to support SQL though. Just putting the link here: http://github.com/quickwit-oss/quickwit Would love to have your feedback on ease of use/perf/whatever here/on twitter/discord ( https://discord.quickwit.io/ ).

Wow man Quickwit looks amazing. Probably would have reached for it when I started Logflare if it was around. I have not seen anything open source that really separates compute and storage like that in one package. You can setup Clickhouse to use an object store but there's a bunch of nuance there. People are starting to hack together something similar using DuckDB on Lambda, basically as a query engine on top of S3.…

thanks :)

I'm convinced that a combo supabase + quickwit can be quite powerful.

It's possible to make Quickwit support simple SQL queries like "SELECT xxx FROM yyy GROUP BY something" quite fast. If you are eager to explore a POC with quickwit, let's have a quick chat, here is my email francois [at] quickwit [dot] io.

Re: Supabase Logs: open-source logging server

#53
post #48

I tried LogFlare (which is now Supabase Logs) in January, but it didn't work well for what I wanted. Supabase Logs / Logflare seems primarily interested in creating graphs from logs rather than using logs for diagnostic purposes. I've been looking for a log solution that's good for the use case of high retention but low volume. I have a few small apps that generate a few MB of logs per month, so basically nothing. Bu…

Appreciate the detailed feedback here.

Frankly these are all things I've wanted to address. We've just had to prioritize other tasks.

We're definitely going to keep iterating.

Thanks for taking the time to try it!

Re: Supabase Logs: open-source logging server

#54

hey 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…

Sorry for off topic question, but do you plan on doing anything about the egress prices?

I do understand that you are hosting your stuff on AWS, which is subject to AWS egress fees, but the egress fee is just way too much for any serious project (imho)

Re: Supabase Logs: open-source logging server

#55

hey 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.

That is no longer true, it is source available, becoming open source after a 3 year embargo period: https://github.com/getsentry/sentry/blob/23.3.1/LICENSE#L19

Re: Supabase Logs: open-source logging server

#57

hey 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…

Sorry for off topic question, but do you plan on doing anything about the egress prices? I do understand that you are hosting your stuff on AWS, which is subject to AWS egress fees, but the egress fee is just way too much for any serious project (imho)

At this stage we're only using AWS for our infra. I wish we could lower the costs, but would be expensive for us to cover the AWS egress charges for all of our customers.

> but the egress fee is just way too much for any serious project

I assume you're not hosting your serious projects on AWS? Do you host them in another cloud provider?

Re: Supabase Logs: open-source logging server

#58
post #50

What are some of the largest production applications built using Supabase? I know it's popular for whipping something up for a hackathon, but how battle tested is it? Also does anybody know what they're doing behind the scenes with the database? I know their storage uses s3, functions (I think) use Deno, this uses BigQuery. Is their db on RDS/Aurora? If so how do they claim max DB size of 1024 TB while Aurora is 128…

- Storage: s3 - Database: EC2 t4g - Functions: Deno

We have tens-of-thousands of applications using Supabase in production. "Size" is a hard one to answer because it means different things to different people. We have projects that have databases and storage in the hundreds-of-terrabytes, projects making millions of API requests, and logos from Fortune 100 companies.

Re: Supabase Logs: open-source logging server

#59

Earlier quoted context omitted.

Sorry for off topic question, but do you plan on doing anything about the egress prices? I do understand that you are hosting your stuff on AWS, which is subject to AWS egress fees, but the egress fee is just way too much for any serious project (imho)

At this stage we're only using AWS for our infra. I wish we could lower the costs, but would be expensive for us to cover the AWS egress charges for all of our customers. > but the egress fee is just way too much for any serious project I assume you're not hosting your serious projects on AWS? Do you host them in another cloud provider?

Why not look into other cloud providers such as Digital Ocean? Much cheaper for compute and bandwidth.

Re: Supabase Logs: open-source logging server

#60

Earlier quoted context omitted.

At this stage we're only using AWS for our infra. I wish we could lower the costs, but would be expensive for us to cover the AWS egress charges for all of our customers. > but the egress fee is just way too much for any serious project I assume you're not hosting your serious projects on AWS? Do you host them in another cloud provider?

Why not look into other cloud providers such as Digital Ocean? Much cheaper for compute and bandwidth.

we are definitely looking at other cloud providers, and slowly moving our infra away from AWS. I don't have any timeline on that - it's hard to migrate all of our databases, while also keeping up with the features that our community are demanding.
Post reply on HN