Exploring observability maturity levels

Before embarking on any multi-year transformational journey, we need to decide on the targets and stages that the organization needs to traverse and achieve. In the case of observability, one good way to frame this is by using maturity levels. A maturity level can be defined as a set of characteristics that an application and its respective teams need to demonstrate in its day-to-day operations based on the application’s criticality, architecture, technology, and business and operational requirements. For example, Application A might be customer-facing, which generates revenue for the organization and hence has a high criticality rating and requires a very high level of maturity compared to Application B, which is used internally by staff. Application B, which does not have any impact on the customers or services the organization provides, needs only a very basic level of maturity.

As part of the observability frameworks, organizations...