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

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

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

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...