Application Performance Monitoring (APM) as a discipline and as a collection of supporting technologies has evolved rapidly since a distinct recognisable market for APM products first emerged in the 2007 - 2008 time frame. While there are many who would argue that APM has mutated into or been replaced by Observability, it makes more sense to see APM as one of many possible use cases now able to exploit the functionalities that Observability brings to the table - particularly when combined with AI.

Let's take a look at the general relationship between Observability and ML and how ML can aid in the conversion of raw telemetry into genuine signals of events or state changes.

When considering the management of telecommunications networks, it might make sense to directly consider the observable data streams available to the practitioner instead of a model-based approach. Learn more in this blog.

In the second part of this blog we will explore how increased entropy forces us to rethink what is required for monitoring.

Observability first emerged as a focal point of interest in the DevOps community in the 2017 time-frame. Aware that business was demanding highly adaptable digital environments, DevOps professionals realised that high adaptability required a new approach to IT architecture.

For the past 20 years, the various stakeholder communities that together constitute the IT industry have attempted to address sustainability. Could observability help in practicing sustainable IT and improving the carbon footprint reduction in its operations?