Skip to main content

Q&A Part Three: Aberdeen Talks About APM

Pete Goldin
APMdigest

In Part Three of APMdigest's exclusive interview, Jim Rapoza, Aberdeen Senior Research Analyst on IT Infrastructure, talks about APM hot topics including Cloud, analytics and NPM.

Start with Part One of the interview with Aberdeen's Jim Rapoza

Start with Part Two of the interview with Aberdeen's Jim Rapoza

APM: In addition to the current challenges of Cloud and mobile - discussed in Part Two of the interview - do you foresee any more long-term challenges to APM?

One challenge I am keeping my eye on is SDN (Software Defined Networking) and OpenFlow. People tend to think of those as strictly network issues but the uptake is super fast. Last year we said SDN was really cutting edge, for universities and leading-edge companies, and we didn't expect it to be a major thing for a while. But by this year there were many companies announcing SDN capabilities, and that is interesting because it changes the nature of networks. It makes networks more like applications. I think APM vendors need to keep an eye on that. It changes the way you approach application performance.

APM: Speaking of networks, in the last few years the term APM has gained significant momentum, as totally separate from NPM. But your report seems to deal with network and application performance together. Do you see APM and NPM converging?

JR: Totally. If you go to the websites of the top 15 APM vendors and the top 15 NPM vendors, you would see a lot of the same terminology. It is all about the applications now.

Traditionally, just go back a couple years, and the NPM vendor would be talking a lot of network terminology. They would mention applications but only in a tangential way. Over the last several months there has been a real focus on applications.

No one really cares how the network is performing. Even when somebody calls IT and says "the network is slow" they really mean "the application is slow". So in the end every issue is just an application issue, and I think we are seeing this realization from NPM vendors. They realize that even though they have a network focus, it is really about application performance. They are just approaching it from the network side.

APM: In your reports you advise to “mind the gap” which I understood as integrating monitoring and management tools better. What is the best way to make sure the tools work together better? Is it about purchasing tools that are more open, or is it about internal integration skills?

JR: I think it is a little bit of both. Obviously you want to be wary of any tool that is completely proprietary and has limited ability to understand or share information. To me, that is a red flag. Tools don't have to be open source, they don't have to provide giant APIs, but you want to see that the product has the ability to work with other systems, and extend, and pull in data from other sources, and export data to other sources. That is getting close to a must-have. As you are building out or upgrading infrastructure, that is something you want to look for. You need to get away from the closed proprietary systems.

APM: In your research on APM in the Cloud, it sounds like fast alerting and response time is a top capability. Why would this be any different from APM in the traditional infrastructure? Why is quick response more important in the Cloud?

JR: You are absolutely right, it is a key factor in traditional infrastructure as well, but when something is completely 100% under your control, then you have a tiny bit more leeway to figure out the situation, to bring applications back up and to understand what happened. In a Cloud-based infrastructure, your margin of error is much lower. You need to be able to address the problem right away.

APM: Your research seems to say that analytics is a key differentiator for success in the Cloud. Is that for the same reason?

JR: Yes, and because in a Cloud-based system you are dealing with different sources of information. You are getting performance data from the Cloud provider, the virtualization management system, and some of your ITSM systems. You can be dealing with 5, 10, 15 different data sources. So having good analytics to be able to parse through all that data - taking that Big Data approach to your performance information - is extremely important.

APM: Plus analytics seems to deliver on several of the top requirements you talk about in the report, like setting baselines and identifying performance patterns.

JR: Yes. This is about visibility. If you don't know what your problems are then you can't fix them. The better analytics and the deeper visibility you have, the closer you are to end-to-end visibility, to find out where problems occur, and figure out a potential problem is going to happen before it actually hits end users. That is the differentiator between success and failure in the Cloud.

APM: Do you have any predictions about how APM is going to evolve in the next year or two?

I think the move from a network focus to an application and end-user focus is going to continue. I think you're going to see more movement toward, if not full on end-to-end, then systems having a lot more openness towards integrating with other systems, to enable end-to-end type capabilities. Obviously there's going to be a lot more built-in capabilities for virtualization, Cloud and mobile, so they can work with those systems seamlessly.

APM: Any upcoming reports that you can tell us about?

I'm going to be looking at the challenges of virtualization and how it is redefining APM. Especially when you start bringing in technologies like VDI. Those are huge impacts on networks and and we need to be aware of how to best optimize networks for delivering virtual desktops.

Another interesting report coming up is on managing performance in companies with wireless networks. That is the way that most companies are going now, and there are different issues when the entire network is entirely wireless.

Related Links:

Read Part One of the interview with Aberdeen's Jim Rapoza

Read Part Two of the interview with Aberdeen's Jim Rapoza

Aberdeen Conducts 2013 Performance Management Survey

Aberdeen Report: The Need for End-to-End Application Performance Management and Monitoring

Jim Rapoza's Blog

ABOUT Jim Rapoza

Jim Rapoza is a Senior Research Analyst focused on the increasing performance pressures that organizations are confronting within their network and application infrastructures. As emerging technologies such as Cloud and mobile change the way that applications are consumed and delivered, dealing with performance issues becomes more complex. Rapoza’s research has examined how organizations are facing these challenges and developing effective solutions to manage network and application performance in today’s complex environments.

For over seventeen years Rapoza has been using, testing, and writing about the newest technologies in software, enterprise hardware and the Internet. He served as the director eWEEK Labs, an award-winning technology testing lab based in Massachusetts and California. Rapoza is also the winner of five awards of excellence in technology journalism, and co-chaired a summit on technology industry security practices. He is a frequent speaker at technology conferences and expositions and has been regularly interviewed as a technology expert by national and local media outlets including CNN, ABC, NPR and the Associated Press.

The Latest
The Latest 10

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

Q&A Part Three: Aberdeen Talks About APM

Pete Goldin
APMdigest

In Part Three of APMdigest's exclusive interview, Jim Rapoza, Aberdeen Senior Research Analyst on IT Infrastructure, talks about APM hot topics including Cloud, analytics and NPM.

Start with Part One of the interview with Aberdeen's Jim Rapoza

Start with Part Two of the interview with Aberdeen's Jim Rapoza

APM: In addition to the current challenges of Cloud and mobile - discussed in Part Two of the interview - do you foresee any more long-term challenges to APM?

One challenge I am keeping my eye on is SDN (Software Defined Networking) and OpenFlow. People tend to think of those as strictly network issues but the uptake is super fast. Last year we said SDN was really cutting edge, for universities and leading-edge companies, and we didn't expect it to be a major thing for a while. But by this year there were many companies announcing SDN capabilities, and that is interesting because it changes the nature of networks. It makes networks more like applications. I think APM vendors need to keep an eye on that. It changes the way you approach application performance.

APM: Speaking of networks, in the last few years the term APM has gained significant momentum, as totally separate from NPM. But your report seems to deal with network and application performance together. Do you see APM and NPM converging?

JR: Totally. If you go to the websites of the top 15 APM vendors and the top 15 NPM vendors, you would see a lot of the same terminology. It is all about the applications now.

Traditionally, just go back a couple years, and the NPM vendor would be talking a lot of network terminology. They would mention applications but only in a tangential way. Over the last several months there has been a real focus on applications.

No one really cares how the network is performing. Even when somebody calls IT and says "the network is slow" they really mean "the application is slow". So in the end every issue is just an application issue, and I think we are seeing this realization from NPM vendors. They realize that even though they have a network focus, it is really about application performance. They are just approaching it from the network side.

APM: In your reports you advise to “mind the gap” which I understood as integrating monitoring and management tools better. What is the best way to make sure the tools work together better? Is it about purchasing tools that are more open, or is it about internal integration skills?

JR: I think it is a little bit of both. Obviously you want to be wary of any tool that is completely proprietary and has limited ability to understand or share information. To me, that is a red flag. Tools don't have to be open source, they don't have to provide giant APIs, but you want to see that the product has the ability to work with other systems, and extend, and pull in data from other sources, and export data to other sources. That is getting close to a must-have. As you are building out or upgrading infrastructure, that is something you want to look for. You need to get away from the closed proprietary systems.

APM: In your research on APM in the Cloud, it sounds like fast alerting and response time is a top capability. Why would this be any different from APM in the traditional infrastructure? Why is quick response more important in the Cloud?

JR: You are absolutely right, it is a key factor in traditional infrastructure as well, but when something is completely 100% under your control, then you have a tiny bit more leeway to figure out the situation, to bring applications back up and to understand what happened. In a Cloud-based infrastructure, your margin of error is much lower. You need to be able to address the problem right away.

APM: Your research seems to say that analytics is a key differentiator for success in the Cloud. Is that for the same reason?

JR: Yes, and because in a Cloud-based system you are dealing with different sources of information. You are getting performance data from the Cloud provider, the virtualization management system, and some of your ITSM systems. You can be dealing with 5, 10, 15 different data sources. So having good analytics to be able to parse through all that data - taking that Big Data approach to your performance information - is extremely important.

APM: Plus analytics seems to deliver on several of the top requirements you talk about in the report, like setting baselines and identifying performance patterns.

JR: Yes. This is about visibility. If you don't know what your problems are then you can't fix them. The better analytics and the deeper visibility you have, the closer you are to end-to-end visibility, to find out where problems occur, and figure out a potential problem is going to happen before it actually hits end users. That is the differentiator between success and failure in the Cloud.

APM: Do you have any predictions about how APM is going to evolve in the next year or two?

I think the move from a network focus to an application and end-user focus is going to continue. I think you're going to see more movement toward, if not full on end-to-end, then systems having a lot more openness towards integrating with other systems, to enable end-to-end type capabilities. Obviously there's going to be a lot more built-in capabilities for virtualization, Cloud and mobile, so they can work with those systems seamlessly.

APM: Any upcoming reports that you can tell us about?

I'm going to be looking at the challenges of virtualization and how it is redefining APM. Especially when you start bringing in technologies like VDI. Those are huge impacts on networks and and we need to be aware of how to best optimize networks for delivering virtual desktops.

Another interesting report coming up is on managing performance in companies with wireless networks. That is the way that most companies are going now, and there are different issues when the entire network is entirely wireless.

Related Links:

Read Part One of the interview with Aberdeen's Jim Rapoza

Read Part Two of the interview with Aberdeen's Jim Rapoza

Aberdeen Conducts 2013 Performance Management Survey

Aberdeen Report: The Need for End-to-End Application Performance Management and Monitoring

Jim Rapoza's Blog

ABOUT Jim Rapoza

Jim Rapoza is a Senior Research Analyst focused on the increasing performance pressures that organizations are confronting within their network and application infrastructures. As emerging technologies such as Cloud and mobile change the way that applications are consumed and delivered, dealing with performance issues becomes more complex. Rapoza’s research has examined how organizations are facing these challenges and developing effective solutions to manage network and application performance in today’s complex environments.

For over seventeen years Rapoza has been using, testing, and writing about the newest technologies in software, enterprise hardware and the Internet. He served as the director eWEEK Labs, an award-winning technology testing lab based in Massachusetts and California. Rapoza is also the winner of five awards of excellence in technology journalism, and co-chaired a summit on technology industry security practices. He is a frequent speaker at technology conferences and expositions and has been regularly interviewed as a technology expert by national and local media outlets including CNN, ABC, NPR and the Associated Press.

The Latest
The Latest 10

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...