Skip to main content

Q&A Part One: Ovum Talks About APM

Pete Goldin
APMdigest

In APMdigest's exclusive interview, Michael Azoff, Principal Analyst at Ovum, talks about his APM Solution Guide 2012, the APM market, and the definition of APM.

APM: How did Ovum's APM Solution Guide come about?

MA: The first time that I wrote about Application Performance Management (APM) was in 2004. The next time I looked at the space was 2008. Now this report is in 2012. So it looks like I'm writing these every four years.

For this report, I was being approached by various vendors, some of them new to the market, and I was very intrigued because they were telling me they were doing all these new things.

At the same time felt that the term APM was very broadly used. There were all these different vendors, they all have different histories, they all have a different take on what APM means and what they offer. So I thought that we really need to get clarification. That was the spark for the report.

Although the Solution Guide does not tend to be exhaustive, I think it is very representative of the leading players in the market. It provides a short analysis of the vendors, and the Ovum APM Rainbow Map which is chart where you can see the features at a glance. It is an opportunity to see what is really happening in APM.

APM: How did you conduct the research?

MA: Mostly talking to the vendors. I had a briefing with each vendor, and I also created a features matrix. The features matrix is a spreadsheet with about 200 rows that we ask vendors to complete. That information is what underlies the Ovum APM Rainbow Map.

APM: What are the most interesting changes you have seen in the current APM market?

MA: I think what we are seeing is that the new infrastructure that is coming out – the Cloud, virtualization – is pushing the envelope for what APM needs to offer. You've also got innovators providing business transaction management, for example. You've got innovation in end-to-end monitoring across a whole range of different edge devices. So I think the industry is very healthy in terms of the innovation that is coming out of it. Some vendors are obviously ahead of others, and I think that is brought out in the report.

APM: Did your research help you come to terms with the definition of APM?

MA: I think APM is still confusing, as a term, because it covers so much. I think end users really need to understand exactly how each vendor is actually using that term, in what it is covering. I think the Solution Guide helps in that respect.

APM: It is interesting that you mention how broad the term APM is, because I see that you include cyber security as an APM capability, and normally I view that as separate from APM. How do you see that fitting in?

MA: Yes, I got a comment from a Gartner analyst querying that. That is an example of where I, as an analyst, am sticking my neck out and saying what the market should be. And the market carries on blithely regardless of my view.

The fact of the matter is that if you look at application development logically, security should be something that developers think about right from the start. I think this is more important today because we are having more applications running outside the firewall. So there is a real need to address these issues.

I don't see a logical separation between security and the rest of application development. I think that application developers should be trained to be aware of security issues, and I think that would make it safer for the end-users. We have profiled this approach in a number of reports in our research. My bringing security into the broader definition of APM is part of that approach, creating awareness. Whether the market embraces that or not is another matter.

APM: Another capability that you included in APM, which I agree with, is network performance management. Explain how you see NPM in relation to APM.

MA: Yes, absolutely. Historically, going back to 2004 and 2008 when I was reviewing the market, the vendors were coming from different traditions, and they were quite separate products. From an end-user point of view, these types of historical divisions don't make any logical sense. They want an application to work, and if there are issues affecting the performance deriving from infrastructure, the information needs to be brought out. So I argued for integrating applications and network right from the early days.

What I think is interesting to see today, is that we are getting nearer to that point. There is greater recognition of the need to have that type of approach. We are seeing vendors embrace that. We are getting nearer to that optimal point where these kinds of historical divisions are not going to affect what kind of product is offered.

We are seeing this crossover between traditional network performance tools that are actually providing a lot of information about applications. So I think we are getting to some interesting crossroads. I take a very broad approach and I think we are seeing that trend in the market.

Click here to read Q&A Part Two: Ovum Talks About APM

Hot Topic
The Latest
The Latest 10

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Q&A Part One: Ovum Talks About APM

Pete Goldin
APMdigest

In APMdigest's exclusive interview, Michael Azoff, Principal Analyst at Ovum, talks about his APM Solution Guide 2012, the APM market, and the definition of APM.

APM: How did Ovum's APM Solution Guide come about?

MA: The first time that I wrote about Application Performance Management (APM) was in 2004. The next time I looked at the space was 2008. Now this report is in 2012. So it looks like I'm writing these every four years.

For this report, I was being approached by various vendors, some of them new to the market, and I was very intrigued because they were telling me they were doing all these new things.

At the same time felt that the term APM was very broadly used. There were all these different vendors, they all have different histories, they all have a different take on what APM means and what they offer. So I thought that we really need to get clarification. That was the spark for the report.

Although the Solution Guide does not tend to be exhaustive, I think it is very representative of the leading players in the market. It provides a short analysis of the vendors, and the Ovum APM Rainbow Map which is chart where you can see the features at a glance. It is an opportunity to see what is really happening in APM.

APM: How did you conduct the research?

MA: Mostly talking to the vendors. I had a briefing with each vendor, and I also created a features matrix. The features matrix is a spreadsheet with about 200 rows that we ask vendors to complete. That information is what underlies the Ovum APM Rainbow Map.

APM: What are the most interesting changes you have seen in the current APM market?

MA: I think what we are seeing is that the new infrastructure that is coming out – the Cloud, virtualization – is pushing the envelope for what APM needs to offer. You've also got innovators providing business transaction management, for example. You've got innovation in end-to-end monitoring across a whole range of different edge devices. So I think the industry is very healthy in terms of the innovation that is coming out of it. Some vendors are obviously ahead of others, and I think that is brought out in the report.

APM: Did your research help you come to terms with the definition of APM?

MA: I think APM is still confusing, as a term, because it covers so much. I think end users really need to understand exactly how each vendor is actually using that term, in what it is covering. I think the Solution Guide helps in that respect.

APM: It is interesting that you mention how broad the term APM is, because I see that you include cyber security as an APM capability, and normally I view that as separate from APM. How do you see that fitting in?

MA: Yes, I got a comment from a Gartner analyst querying that. That is an example of where I, as an analyst, am sticking my neck out and saying what the market should be. And the market carries on blithely regardless of my view.

The fact of the matter is that if you look at application development logically, security should be something that developers think about right from the start. I think this is more important today because we are having more applications running outside the firewall. So there is a real need to address these issues.

I don't see a logical separation between security and the rest of application development. I think that application developers should be trained to be aware of security issues, and I think that would make it safer for the end-users. We have profiled this approach in a number of reports in our research. My bringing security into the broader definition of APM is part of that approach, creating awareness. Whether the market embraces that or not is another matter.

APM: Another capability that you included in APM, which I agree with, is network performance management. Explain how you see NPM in relation to APM.

MA: Yes, absolutely. Historically, going back to 2004 and 2008 when I was reviewing the market, the vendors were coming from different traditions, and they were quite separate products. From an end-user point of view, these types of historical divisions don't make any logical sense. They want an application to work, and if there are issues affecting the performance deriving from infrastructure, the information needs to be brought out. So I argued for integrating applications and network right from the early days.

What I think is interesting to see today, is that we are getting nearer to that point. There is greater recognition of the need to have that type of approach. We are seeing vendors embrace that. We are getting nearer to that optimal point where these kinds of historical divisions are not going to affect what kind of product is offered.

We are seeing this crossover between traditional network performance tools that are actually providing a lot of information about applications. So I think we are getting to some interesting crossroads. I take a very broad approach and I think we are seeing that trend in the market.

Click here to read Q&A Part Two: Ovum Talks About APM

Hot Topic
The Latest
The Latest 10

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...