Yep, my post was just saying this is observability 0.5, not 2.0. However, I actually do agree that you should prefer observability 0.5 in most cases if you hav

Yep, my post was just saying this is observability 0.5, not 2.0. However, I actually do agree that you should prefer observability 0.5 in most cases if you have a appropriate implementation. I am familiar with time travel debugging where you use automatic event instrumentation to stream GB/s per core to fully and perfectly reconstruct all program states. The problems and solutions I see being proposed in the distributed tracing space seem so grotesquely inefficient, yet actionable data anemic in comparison that I am pretty sure most of the limits preventing “just events” are due to inadequate implementations. However, if you really are running into limits, then it is important to have these known fallback mechanisms instead of just ignoring their existence and calling it a 2.0.