I think I agree to some extent. I like parts of all 3 definitions presented here, and I feel the new definition loses some of the clarity by omitting the fact t

I think I agree to some extent. I like parts of all 3 definitions presented here, and I feel the new definition loses some of the clarity by omitting the fact that we’re interested in a particular system at a time. But I really like this blog post’s main thesis that the people are part of the system and a key part of your observability stack. You can have an objectively perfectly observable system that outputs all of its answers to your questions in Greek, and I won’t be able to make head nor tail of it and neither will pretty much any of my team. Just as nines don’t matter if the users aren’t happy, observability doesn’t matter if the team can’t understand and act on the answers. I have spent the last year building out observability tooling and I expect to spend another year on it. I would say 70% of my problems to solve are social rather than technical.