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

IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

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

IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...