You're logging wrong

Ah yeah I thought it was weird when a Theo video less than 30 minutes dropped

I apologize for the issue we had on this video earlier. I will do better, the editing mistake was on me.

IF YOU SAW THIS BEFORE, START AT 8:30 Sorry about the issues - bad export before and a ton of the video was missing 🙃

First non-AI video in a while, this is refreshing 👏

I was afraid I forgot to take my medication and imagined a video about logging this morning out of insanity...

OTel + Contextual logging literally solves this.

So a quick google shows that Zipkin shows what appears to be a fairly stable/mature project with a 9+ year history, 18k stars and almost 200 contributors. Not saying you're obligated to look up that project just because a commenter mentioned it, but idk sometimes you gotta humble yourself mate. This has "mongodb guy didn't recognise me" vibes. "I haven't heard of it already so it's worthless".

9:30 If you can't do it then you're using it wrong lol. It's called spans with trace ids, just ask you buddy opus 'bout it.

Just keep in mind that fields like emails, filenames, and form inputs should never show up in logs, since then anything (or anyone) with access to your log platform has access to user data. These should be pseudonymized so that customer data cannot be read from logs (on purpose or accidentally). Instead, user data should have a separate need-to-know lookup system which includes access history record-keeping and regular auditing of all access events. Generally, it's also a good idea to have a technical barrier which prevents access to customer data unless that specific customer grants access to the specific data needed for investigation. At least, this is true for business software...maybe things are different elsewhere.

INSTANTLY changed how I handle logging. Real banger.