It was also determined that the value of the Observability insights depended on two other major factors: the quality of the measurements from which the insights were generated and the temporality of those measurements. In other words, noisy data would lead to noisy, poor-value insights. Measurements also needed to provide insight into what was happening, what had happened, causality and, ultimately, forecasts of what would happen.
We developed an Observability Strategy based on a Maturity Model that defined each degree of Observability: Insight, Quality and Temporality, and linked them together to provide a common, scalable framework that enabled the customer to determine and communicate their approach to increasing the Observability of their IT systems. We assessed their current situation in terms of the model and proposed a roadmap for developing the Observability capability.
The customer accepted our Observability Strategy and is currently in the process of deploying it across their organisation.