Skip to main content

How AIOps Defuses the Impact of Change

Phil Tee

When you see distressing internet outages occur like the recent Fastly incident that threw a slew of websites offline, I am never surprised by how widespread the problem was, but paradoxically that it wasn't worse.

The infrastructure behind our digital world is mind-numbingly complex. The movement to cloud computing has added even more layers to the interconnectedness. So when a simple software update goes awry, despite the best efforts of quality control, the ripple effects can go far and wide. The digital economy in the US alone accounts for at least $1,849 billion annually, according to a 2020 report by the Bureau of Economic Analysis. So every moment offline matters.

Prompt troubleshooting is a herculean task — impossible, really, for the human mind alone. There's just too much information to sift through to quickly identify how a single change event precipitated such a widespread crash. IT teams must rely on artificial intelligence, machine learning and algorithms to find and repair the root cause of the problem.

The Perils of "Change"

What seems near effortless online to most of us — ordering food, a Zoom call, reading this article — is a staggeringly Byzantine interconnected flow of data packets, routers, modems, internet service providers, gateways, network exchanges, servers and applications. The interdependencies are at such a level that any meaningful amount of mappability is out of reach. For a human mind, you're talking about understanding more interdependencies than particles in the observable universe — a stunning amount of complexity.

Amid that landscape is the need to update software, whether to refresh the operating system, add features or bolster security. And from time to time, someone performs a routine update that has an unintended and unforeseen consequence. Identifying a problem before an outage occurs is largely a fool's errand because the scale of the situation is just too great. The key is to find the problem before a widespread outage occurs. In such an interconnected digital world, errors tend to cascade and propagate. Catching them early is paramount.

One simple update that goes awry could cripple e-commerce if widespread system outages lingered. The potential risk is profound. History has shown when unintended consequences snowball. Mexico reeled in the 1990s from the devaluation of the peso. The United States stumbled in the 2000s when collateralized debt obligations tied to the mortgage industry prompted a financial crisis.

To be clear, the Fastly incident wasn't a global crisis. The Fastly team responded remarkably well. But the outage underscored how trouble quickly can spread in the interconnected digital world. What's absolutely necessary is to pinpoint the problem immediately.

How Intelligent Observability Defuses the Threat

This is where intelligent observability comes in to analyze the impact of change. AIOps with observability work together to quickly spot the patterns and interconnections in the application data to identify the root cause of a problem before it cascades further and causes a widespread outage.

Every change, every software update, has some kind of record associated with it. So theoretically, when something goes wrong, a site reliability engineer or other IT expert would get an alert in which they could simply trace the issue back to the record of the change that triggered the issue. But in practice, the situation is very complicated. Thousands of other data points were created before and after this specific change occurred, so the challenge to identifying the root cause of the problem is linking the right data to the relevant change.

AIOps finds the right data. It applies algorithms to observability data such as metrics, logs and traces to identify anomalies, determine event significance, surface meaningful alerts and correlate data to provide valuable context. Observability makes the job easier by engineering the application infrastructure to make all of the data more observable. AIOps surfaces the right data amid an ocean of data so your IT teams can quickly spot and repair the problem.

Every change, every software update, leaves a clue behind. The problem is there are thousands and thousands of potential suspects. Intelligent observability can quickly solve the "whatdunnit" before any outage becomes much worse.

The Latest

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...

How AIOps Defuses the Impact of Change

Phil Tee

When you see distressing internet outages occur like the recent Fastly incident that threw a slew of websites offline, I am never surprised by how widespread the problem was, but paradoxically that it wasn't worse.

The infrastructure behind our digital world is mind-numbingly complex. The movement to cloud computing has added even more layers to the interconnectedness. So when a simple software update goes awry, despite the best efforts of quality control, the ripple effects can go far and wide. The digital economy in the US alone accounts for at least $1,849 billion annually, according to a 2020 report by the Bureau of Economic Analysis. So every moment offline matters.

Prompt troubleshooting is a herculean task — impossible, really, for the human mind alone. There's just too much information to sift through to quickly identify how a single change event precipitated such a widespread crash. IT teams must rely on artificial intelligence, machine learning and algorithms to find and repair the root cause of the problem.

The Perils of "Change"

What seems near effortless online to most of us — ordering food, a Zoom call, reading this article — is a staggeringly Byzantine interconnected flow of data packets, routers, modems, internet service providers, gateways, network exchanges, servers and applications. The interdependencies are at such a level that any meaningful amount of mappability is out of reach. For a human mind, you're talking about understanding more interdependencies than particles in the observable universe — a stunning amount of complexity.

Amid that landscape is the need to update software, whether to refresh the operating system, add features or bolster security. And from time to time, someone performs a routine update that has an unintended and unforeseen consequence. Identifying a problem before an outage occurs is largely a fool's errand because the scale of the situation is just too great. The key is to find the problem before a widespread outage occurs. In such an interconnected digital world, errors tend to cascade and propagate. Catching them early is paramount.

One simple update that goes awry could cripple e-commerce if widespread system outages lingered. The potential risk is profound. History has shown when unintended consequences snowball. Mexico reeled in the 1990s from the devaluation of the peso. The United States stumbled in the 2000s when collateralized debt obligations tied to the mortgage industry prompted a financial crisis.

To be clear, the Fastly incident wasn't a global crisis. The Fastly team responded remarkably well. But the outage underscored how trouble quickly can spread in the interconnected digital world. What's absolutely necessary is to pinpoint the problem immediately.

How Intelligent Observability Defuses the Threat

This is where intelligent observability comes in to analyze the impact of change. AIOps with observability work together to quickly spot the patterns and interconnections in the application data to identify the root cause of a problem before it cascades further and causes a widespread outage.

Every change, every software update, has some kind of record associated with it. So theoretically, when something goes wrong, a site reliability engineer or other IT expert would get an alert in which they could simply trace the issue back to the record of the change that triggered the issue. But in practice, the situation is very complicated. Thousands of other data points were created before and after this specific change occurred, so the challenge to identifying the root cause of the problem is linking the right data to the relevant change.

AIOps finds the right data. It applies algorithms to observability data such as metrics, logs and traces to identify anomalies, determine event significance, surface meaningful alerts and correlate data to provide valuable context. Observability makes the job easier by engineering the application infrastructure to make all of the data more observable. AIOps surfaces the right data amid an ocean of data so your IT teams can quickly spot and repair the problem.

Every change, every software update, leaves a clue behind. The problem is there are thousands and thousands of potential suspects. Intelligent observability can quickly solve the "whatdunnit" before any outage becomes much worse.

The Latest

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...