Supabase + Oodle: Because database logs deserve love too
All logs belong together
Last week, Supabase launched Log Drains. Today, we're launching Oodle's native integration for Supabase.
Better Together
As an engineer I prefer to have one unified way to look at all my logs. As a cost and token-conscious engineer, I prefer one simple API / CLI / MCP that my AI agent can use to gather context and debug.
There are many many ways to get your logs into Oodle. Using CloudWatch logs? Or just dumping the logs into S3? Google Stackdriver? Oodle covered all that, and more. But, till last week, not Supabase.
Sup, Supabase?
Now that Supabase has started supporting sending logs out, you can get them into Oodle.
Supabase users know the drill: something breaks, it was a constant back-and-forth between Supabase logs and the rest of the logs. Oodle's deep integration with structured logs from Supabase eliminates this.
Users love Oodle logs because queries are fast, storage is cost-effective, and structured logs are treated with the love and attention to detail that they deserve. And now the same extends to Supabase logs as well.
- Check out our supabase docs
- Learn more about what Oodle offers
- Play around with Oodle playground