Rivian lost my full payment for an R1S.

That's astonishing. What ended up happening?

What was the outcome? Free car? A strongly worded letter and you wrote another check?

Not a free car because I paid them.

Funny enough their dashboard showed a payment so I just screenshot that for them to look up in their own db!

btw recently cleaned up my wal cache busting code quite a bit if you're interested.

https://github.com/Logflare/logflare/blob/main/lib/logflare/...

Need to make a lib out of this!!

Thanks from one Elixir-using Chase to another ;)

I've helped with this one. Happy to answer any questions also.

We use :telemetry to collect usage data per tenant for Supabase Realtime.

We do this for rate limiting but it also makes it very easy for us to attach a listener (https://github.com/supabase/realtime/blob/main/lib/realtime/...) which ships these (per second) aggregates to BigQuery (via Logflare), which then the billing team can aggregate further to display and actually bill people with.

Thanks for sharing!

We just had some orphaned database connections (our bug) to a tenant and were able to find and kill them because of Erlang's observability:

https://gist.github.com/chasers/e4aa33625e6ea39ecb89f03383dd...

edit: link to gist

Not possible in your typical Rails setup where remote console spawns a separate process so you can't inspect what's going on with your actual servers. Even if so, the amount of observability is not remotely (pun intended) close. You don't appreciate it until your production puma workers start going haywire and you have no idea why

You can attach to a running Ruby process with rbtrace easily.

Yo :D This is what Supabase Realtime does!

https://github.com/supabase/realtime

Spin up a Supabase database and then subscribe to changes with WebSockets.

You can play with it here once you have a db: https://realtime.supabase.com/inspector/new

Yeah, Supabase is awesome. In fact, WalEx originally started out as stolen code from realtime so I could do stuff right in Elixir (biz logic).

supabase dev here...

this was a very fun load test to run. happy to answer any questions.

shoutout to José Valim and the Dashbit team for the help on Supavisor. elixir and erlang are amazing tools.

connection limits, even with pgbouncer, have been a big support burden for us. supavisor should let us be more liberal with connections we allot to folks.

supavisor is rolled out and available for all projects to use today. contact support[0] and we can expose the supavisor connection string in your dashboard. we'll be proactively exposing it to everyone gradually over the next ~1 month. we'll run pgbouncer and supavisor both for you for probably ~5 months before you need to switch to supavisor.

also very excited at the potential features a custom postgres proxy can unlock.

[0] https://supabase.com/dashboard/support/new

yes otel across all of Supabase in on our radar for sure. we just added ingest support for otel payloads to Logflare (docs coming soon) so when we have that you'll get them on the platform and locally.

if you haven't seen the metrics endpoint we do have an endpoint you can scrape for all your Supabase metrics, and we just improved the example repo quite a bit on how to ship those somewhere: https://github.com/supabase/grafana-agent-fly-example/

> although ensuring that only a single client is writing to a database at any time is (mostly) left to the application

Sounds like trouble.

I hadn't seen WalEx. Looks rad!!

It’s mostly just ripped off code from Supabase and refactored to use Postgrex Replication based on the video you did.