Skip to main content

APM, Observability and AIOps - a Way Forward

Ron Williams
Gigaom

What's coming in operations management tooling? In a nutshell, a shift from observability to intelligent operations and the longer-term move towards AI-enabled operations in support of the business, but application performance management (APM) still has a place.

Let's break these pieces down. First, APM could be perceived as becoming passé, in tooling terms. All larger companies use it, and tools vendors pull it into their observability suites. Companies still need APM as a starting point if they are unready for the integration heavy lifting, coordination between multiple departments, and political capital that more advanced solutions require.

Many vendors recognize this, selling APM at a reasonable cost with bundled access to other features — but there's a catch. Historically, APM licensing has been based on users, rather than data consumed. But now, vendors are using data as the driving factor for cost. The focus now is on data consumption models: If you're consuming a certain volume of logs, telemetry, and traces, these will drive your cost.

This means less predictability. If someone is temporarily consuming a lot of data, even legitimately (for example, for a new project), they'll have a blip in their billing. In addition, a user can say, "Oh, I can use this feature too," meaning they consume more data, which makes more money for vendors. APM is almost the gateway drug to observability, feature by feature.

Some companies make it easier for you to add another of their little tools because it's convenient. One company has 26 products — if you use one, you can access the others. Suddenly, finance goes, "Wait a minute, why do we suddenly have this big cost increase?" And you have to go back and look and realize, "Oh, George added this one, Sarah used that one, and Sam used the other one, and wow, our bill just quadrupled."

We're also seeing the rise of generative AI in Ops. Predictive AI and machine learning have long been in the mix, but this is the first year that genAI will appear in products. I expect every vendor will offer something related, but the offerings will almost universally be bad. It's not the vendors' fault, but nobody knows what we can, or should be doing with this capability. So vendors will include the feature, whether or not it's useful or really answers the questions businesses have.

For this reason, I'm updating one of my models. Historically, I have shown the evolution from monitoring to observability to awareness. This year, I'll change from monitoring to observability to intelligence. Under "intelligence" I have questions such as:

Is the business OK?

What was the result of last month's marketing campaign?

Sales has a new initiative; what will impact our services and support?

Unless you're in the business of IT, your real questions are not about IT but the business. If you fly people from point A to point B, you want to ask questions about that, not whether the revenue management system is working.

Observability didn't look to answer these questions, but now that we have more intelligence in tools, we must address them. You want to ask your chat interface that connects to your AIOps that question, rather than going over to revenue management and then going over to this group, that group, or the other group, for the answers.

These tools still have the same problems with AI: choosing the right algorithm at the right time, explainable AI, and AI bias — these are not going away. Let's say I train my AI on all my data … stop there, I don't have all my data because, for example, the guys over in desktop support didn't want to give me their data, but the guys over in networking did. I've trained the models on network data, and the AI now knows networking. So, what is every problem going to be? You guessed it, a networking problem.

Being able to train the AI and getting beyond its biases are going to be challenging. Additionally, generative AIs can hallucinate, presenting nonsense data as fact. Trusting AI as we train it to learn our businesses and help us run more efficiently is part of the new paradigm in business operations.

That'll set the scene for 2024: I expect them to have something, but it won't really help. It may be a little more focused in 2025, but by year three and on — that's when I really believe the AI they're putting into some of these tools will be truly useful. That is, it can answer questions about the condition of the enterprise, not the condition of IT.

That's the direction I see the industry taking, and I'm pushing to see how vendors will impact how the entire business operates. In three years, we should see the hype turn into real changes. For now, the nascent large language models show promise; but with planning and focus, generative AI won't be another promise broken.

Ron Williams is an Analyst at Gigaom

The Latest

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 ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

APM, Observability and AIOps - a Way Forward

Ron Williams
Gigaom

What's coming in operations management tooling? In a nutshell, a shift from observability to intelligent operations and the longer-term move towards AI-enabled operations in support of the business, but application performance management (APM) still has a place.

Let's break these pieces down. First, APM could be perceived as becoming passé, in tooling terms. All larger companies use it, and tools vendors pull it into their observability suites. Companies still need APM as a starting point if they are unready for the integration heavy lifting, coordination between multiple departments, and political capital that more advanced solutions require.

Many vendors recognize this, selling APM at a reasonable cost with bundled access to other features — but there's a catch. Historically, APM licensing has been based on users, rather than data consumed. But now, vendors are using data as the driving factor for cost. The focus now is on data consumption models: If you're consuming a certain volume of logs, telemetry, and traces, these will drive your cost.

This means less predictability. If someone is temporarily consuming a lot of data, even legitimately (for example, for a new project), they'll have a blip in their billing. In addition, a user can say, "Oh, I can use this feature too," meaning they consume more data, which makes more money for vendors. APM is almost the gateway drug to observability, feature by feature.

Some companies make it easier for you to add another of their little tools because it's convenient. One company has 26 products — if you use one, you can access the others. Suddenly, finance goes, "Wait a minute, why do we suddenly have this big cost increase?" And you have to go back and look and realize, "Oh, George added this one, Sarah used that one, and Sam used the other one, and wow, our bill just quadrupled."

We're also seeing the rise of generative AI in Ops. Predictive AI and machine learning have long been in the mix, but this is the first year that genAI will appear in products. I expect every vendor will offer something related, but the offerings will almost universally be bad. It's not the vendors' fault, but nobody knows what we can, or should be doing with this capability. So vendors will include the feature, whether or not it's useful or really answers the questions businesses have.

For this reason, I'm updating one of my models. Historically, I have shown the evolution from monitoring to observability to awareness. This year, I'll change from monitoring to observability to intelligence. Under "intelligence" I have questions such as:

Is the business OK?

What was the result of last month's marketing campaign?

Sales has a new initiative; what will impact our services and support?

Unless you're in the business of IT, your real questions are not about IT but the business. If you fly people from point A to point B, you want to ask questions about that, not whether the revenue management system is working.

Observability didn't look to answer these questions, but now that we have more intelligence in tools, we must address them. You want to ask your chat interface that connects to your AIOps that question, rather than going over to revenue management and then going over to this group, that group, or the other group, for the answers.

These tools still have the same problems with AI: choosing the right algorithm at the right time, explainable AI, and AI bias — these are not going away. Let's say I train my AI on all my data … stop there, I don't have all my data because, for example, the guys over in desktop support didn't want to give me their data, but the guys over in networking did. I've trained the models on network data, and the AI now knows networking. So, what is every problem going to be? You guessed it, a networking problem.

Being able to train the AI and getting beyond its biases are going to be challenging. Additionally, generative AIs can hallucinate, presenting nonsense data as fact. Trusting AI as we train it to learn our businesses and help us run more efficiently is part of the new paradigm in business operations.

That'll set the scene for 2024: I expect them to have something, but it won't really help. It may be a little more focused in 2025, but by year three and on — that's when I really believe the AI they're putting into some of these tools will be truly useful. That is, it can answer questions about the condition of the enterprise, not the condition of IT.

That's the direction I see the industry taking, and I'm pushing to see how vendors will impact how the entire business operates. In three years, we should see the hype turn into real changes. For now, the nascent large language models show promise; but with planning and focus, generative AI won't be another promise broken.

Ron Williams is an Analyst at Gigaom

The Latest

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 ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...