I think this blog post uses a lot of words to not say much; maybe useful as an exercise in burying the lede? I read the whole thing and it matches what I consi

I think this blog post uses a lot of words to not say much; maybe useful as an exercise in burying the lede? I read the whole thing and it matches what I consider to be important in observability ("Help me make a decision"), but the point is so spread out, and so diluted that I'm not even sure that it is there at all. So, firstly, here's two easy and simple rules for technologists trying to satisfy the audience for the observability outputs: 1. If what you get out of the observability exercise/process/tools doesn't help make a decision, that's not observability, it's trivia. 2. If you're making decisions without any data or with insufficient data, then you don't have any (or have insufficient) observability. Depending on the audience, different people make different decisions. Secondly, here's a cheat-sheet to help: https://www.rundata.co.za/rundata/blog/chap2/content.html https://www.rundata.co.za/rundata/blog/chap2/content.html