Apr 2026 Update
We are live on Auth0 marketplace! Excited to help Auth0 customers elevate their observability.
Just the other day I wrote: "All logs belong together", referring to Supabase logs. It reminded me of another important category of logs which usually do not reside with the app and infra logs: Auth logs.
Solving our own problem
Oodle would not be an observability company worth its name if we didn't have extensive instrumentation of our own code and infrastructure. We have deep visibility into our own Kubernetes clusters, AWS resources, and CI.
That's exactly why it was annoying when we realized our AI Assistant could debug deployment failures, trace an HTTP request end-to-end, root-cause gnarly Kubernetes issues with ease; yet, was utterly helpless when it came to debugging auth issues.
Of course! Auth0 logs were not flowing into Oodle!
Using Auth0's custom log streams, we started sending logs to Oodle, only to realize we don't know what fi, flo and many other short codes mean! We are glad though that Auth0 publishes a reference. Since we were not really thrilled to debug with cryptic logs, we built lookup table-based log enrichment.
Solving customers' problems
Few weeks later, a prospect asked "Can I use some kind of a lookup to enrich my logs?"
We were happy! "Glad you asked ..."
I am not kidding, the next question was "Can I route Auth0 logs to Oodle?"
We were super happy! "Glad you asked ..."
It was good to know we were not isolated in these problems. Even better that these features helped us close a deal faster!
Don't forget to launch loudly!
Oh, but we did!
We have been using Auth0 logs and lookup-table-based enrichment in production, and so have our customers. No launch post, no announcements, just docs, and happy users.
While writing about Supabase logs, it hit me that it's not about the features in isolation. It is about a crucially important point: "All logs belong together". A big, unified, comprehensive pool of logs keeps engineers happy and AI agents productive.
So I am writing this post just to reiterate the point.
Did I tell you...
Auth0 sends structured logs, and Oodle makes full use of the structure. You can query, filter, and visualize based on arbitrarily nested fields sent by Auth0.
Almost forgot!
Multi-week retention of logs on Auth0 will break your bank, even multi-month log retention on Oodle won't.
If you already use Oodle and Auth0, give it a go: us1, ap1. Otherwise, come on in, we've got a generous free tier!
