The world is messy and chaotic, who knew?! Embracing that hard fact can bring relief and be a first step to understanding how to handle known knowns, unknown unknowns and all that jazz.

In today's Architecture Weekly edition, I summarised what we learned so far in "observability editions." I explained my thoughts on correlating product and technical observability. So, how to deal with reality and set and verify our expectations.

To get the most out of chaotic worlds, we need to clearly define our known-knowns, known-unknowns, and unknown-unknowns, as that's the basis for selecting the right tools.

We can also correlate that with our own, users', and vendors' expectations. By making our system observable, we're getting the tools to not only do technical troubleshooting but also analyse and gain more insights.

Still, we need not forget about the mechanical sympathy and keeping it real, e.g. think about the costs and needed effort to incorporate all of that.

That's also the reason why I not only showed my way, but got great guests like Gojko Adzic and Jarosław Pałka recently to show various perspectives and use cases.

Even though our backgrounds differed, the conclusion was the same: we need to make our system observable. Without that, we leave our products with no traces. (pun intended)

How do you deal with it?