Recording available: And it’s live: youtu.be/ad42UTjP7ds

But to also know that it'll be recorded along with all my other attributes that I wrote down in the span so that I can slice and dice things in any way I want later on. So in short - yeah agreed about the wide event idea! And I do appreciate finding names to call these practices, so thanks for that!

I've always found it handy to be able to add some instrumentation in my code, and know that it'll show up as a dashboardable/alarmable metric with a predictable dimensionality (to balance cost with performance).