Thanks! Bookmarking this for a slow read.

Thank you!!!

Thank you so much!!!!!!
It's super early here. I'll watch with coffee once the sun is up.

It's when you can't troubleshoot the setup, and you're left with trial and error, and a need for even more coffee

Github 😍

The cat photos are priceless. Really keen to see how people are dealing with decoupling to solve complexity, especially when not everything is "pure".

Is there a chance to watch a replay somewhere please?

+1

It's great. I love how the approach relates back to SLSA and that this is fundamentally a directed acyclic graph.

Liked the 'AI hype' pop culture moment

Trying to think of what processing would happen at source (home of children getting toy)... situational awareness... but this is where the analogy breaks down a bit

Toy breakages, chimney malfunctions, bio break latency, reindeer torque

But where's our Buffy content.... 😂

I hear you and I have similar needs to vent. For me, APM is the true COBOL here. #MELT should be #MELTS (S for situation). Not treating stitching situational awareness in as a first class citizen in the #observability mental model is why the zombies are able to get to their prey!

it's a good metaphor, though I think it downplays the processing at the source.

A fun idea - what if Mrs Klaus was watching Mr Klaus doing his Xmas deliveries globally with OTEL. How and why would we configure agents, collector agents, collector gateways, and where would pipelines be laid down?

Nice work. The postal analogy works pretty well. Good explanation of the delivery mechanism across the agents, collector configuration. Pity it doesn't delve into the processing differences, to explain the decoupling some more.

I hear you!!!

This happened to me at a conference last year - all the photos I took during demo were unreadable.

😆