Skip to main content

30 Ways APM Should Evolve - Part 4

APMdigest asked the top minds in the industry what they feel is the most important way Application Performance Management (APM) tools must evolve. The recommendations on this list provide a rare look into the long-term future of APM technology. Part 4 covers the end user experience.

Start with 30 Ways APM Should Evolve - Part 1

Start with 30 Ways APM Should Evolve - Part 2

Start with 30 Ways APM Should Evolve - Part 3

16. END USER EXPERIENCE

In this era of digital transformation, delivering an exceptional end user experience is one of the most important goals for enterprises. APM must evolve into a unified monitoring solution that shows a clear linkage to the quality of the end user experience. Additionally, monitoring of the supporting infrastructure is another critical component in delivering the best overall experience to the end-users of the application.
Peter Kacandes
Senior Product Marketing Manager, AppDynamics

Because user experience is the new service level agreement standard, businesses must arm themselves with APM tools that natively provide end-to-end visibility into user experience across mobile, web and e-commerce platforms, monitoring and analyzing API calls, runtime environments, and business transactions in the context of user actions and their devices.
Monica Benjamin
Director of Product Marketing, HPE Software

Read Monica Benjamin's blog: APM Evolution - End User Experience

According to a recent Gartner survey, 46 percent of enterprises view end-user experience monitoring (EUEM) as the most important APM dimension, and 49 percent cite "enhance customer service quality" as their first choice for rationalizing APM purchases. Companies know the end-user experience impacts the bottom line, but they have trouble quantifying exactly how much. APM must evolve to enable not only better understanding of the end-user experience, but also the direct business impact of poor performance. This will drive future APM investments.
Dennis Callaghan
Director of Industry Innovation, Catchpoint

APM tools need to get as close as possible to the end users. That could mean putting them into mobile apps and browsers, running playback-bots, or implementing in-app customer feedback mechanisms. That's the most important way APM tools must evolve. Traditionally, APM tools have focused largely on monitoring internal, full app stacks inside the data center. Now, we're seeing more consolidation in the application development and deployment stack – for instance, AWS for hosting and NoSQL as the preferred database technology. That means APM tools will gradually shift from lower-level challenges (monitoring apps, servers, and databases) to higher-level ones. These new challenges would include things like a) understanding user behavior and tying it back to the application developers' world via time-based hooks and b) knowing that a new workflow is turning more Android users away than the previous flow. That kind of insight is what today's app developers should expect from an APM tool.
Dev Anand Ramasamy
Director of Product Management, ManageEngine

17. END-USER EXPERIENCE + ROOT CAUSE ANALYSIS

The APM tools today measure and expose the latency and availability of digital services. In order to offer the owners of these services a better overview and control of user experience, the APMs will need to add two additional dimensions to their dashboards – tracing of users and root cauuses. The APMs of tomorrow will have to monitor the experience of individual users and when the experience is not satisfying, expose root causes with the precision of a specific line in source code.
Ivo Mägi
Co-founder and Head of Product, Plumbr

18. DIGITAL PERFORMANCE MANAGEMENT

Application Performance Management tools must evolve to become Digital Performance Management. As the definition of "application" is both expanding and becoming more vague, it's important for these tools to focus on the customer experience end-to-end. That's essentially what we mean by digital performance.
Jason Bloomberg
President, Intellyx

APM has historically been IT-centric, driven by operations and development, mainly to more efficiently identify and fix issues. However, this gives little or no thought to the digital customer experience. The most successful businesses are practicing what we call Digital Performance Management (DPM), using customer experience insights as a common language to foster collaboration and align priorities across these teams including business stakeholders. DPM collected analytics are uniquely positioned to help break silos by providing detailed insight around user behavior, delivered experience quality and the supporting applications and infrastructure health and performance across channels.
Erwan Paccard
Director of Customer Experience Marketing, Dynatrace

2016 will see the beginning of a mass transition from APM to DPM (Digital Performance Management) with emphasis on front-end performance measurement, testing and optimization based on analytics insights gained from the holy trinity of data - real user, business outcome and ops metrics.
Ann Ruckstuhl
CMO, SOASTA

19. APPLICATION-AWARE APM

The biggest evolution in application performance management will be application-aware solutions in the virtualized environment that tie the end user to the virtualized infrastructure that is delivering the application. As the management interface grows increasingly complex with virtual machines, hybrid cloud and hypervisor-based solutions, an evolution must take place to ensure that IT understands how their business critical applications are using compute, storage, network and virtualization resources on a user-by-user basis. As IT continues to evolve, monitoring solutions must also evolve to provide complete transparency throughout applications and all infrastructure layers.
Simon Taylor
President, Comtrade Software

Read 30 Ways APM Should Evolve - Part 5, covering the impact of APM on the Business.

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...

30 Ways APM Should Evolve - Part 4

APMdigest asked the top minds in the industry what they feel is the most important way Application Performance Management (APM) tools must evolve. The recommendations on this list provide a rare look into the long-term future of APM technology. Part 4 covers the end user experience.

Start with 30 Ways APM Should Evolve - Part 1

Start with 30 Ways APM Should Evolve - Part 2

Start with 30 Ways APM Should Evolve - Part 3

16. END USER EXPERIENCE

In this era of digital transformation, delivering an exceptional end user experience is one of the most important goals for enterprises. APM must evolve into a unified monitoring solution that shows a clear linkage to the quality of the end user experience. Additionally, monitoring of the supporting infrastructure is another critical component in delivering the best overall experience to the end-users of the application.
Peter Kacandes
Senior Product Marketing Manager, AppDynamics

Because user experience is the new service level agreement standard, businesses must arm themselves with APM tools that natively provide end-to-end visibility into user experience across mobile, web and e-commerce platforms, monitoring and analyzing API calls, runtime environments, and business transactions in the context of user actions and their devices.
Monica Benjamin
Director of Product Marketing, HPE Software

Read Monica Benjamin's blog: APM Evolution - End User Experience

According to a recent Gartner survey, 46 percent of enterprises view end-user experience monitoring (EUEM) as the most important APM dimension, and 49 percent cite "enhance customer service quality" as their first choice for rationalizing APM purchases. Companies know the end-user experience impacts the bottom line, but they have trouble quantifying exactly how much. APM must evolve to enable not only better understanding of the end-user experience, but also the direct business impact of poor performance. This will drive future APM investments.
Dennis Callaghan
Director of Industry Innovation, Catchpoint

APM tools need to get as close as possible to the end users. That could mean putting them into mobile apps and browsers, running playback-bots, or implementing in-app customer feedback mechanisms. That's the most important way APM tools must evolve. Traditionally, APM tools have focused largely on monitoring internal, full app stacks inside the data center. Now, we're seeing more consolidation in the application development and deployment stack – for instance, AWS for hosting and NoSQL as the preferred database technology. That means APM tools will gradually shift from lower-level challenges (monitoring apps, servers, and databases) to higher-level ones. These new challenges would include things like a) understanding user behavior and tying it back to the application developers' world via time-based hooks and b) knowing that a new workflow is turning more Android users away than the previous flow. That kind of insight is what today's app developers should expect from an APM tool.
Dev Anand Ramasamy
Director of Product Management, ManageEngine

17. END-USER EXPERIENCE + ROOT CAUSE ANALYSIS

The APM tools today measure and expose the latency and availability of digital services. In order to offer the owners of these services a better overview and control of user experience, the APMs will need to add two additional dimensions to their dashboards – tracing of users and root cauuses. The APMs of tomorrow will have to monitor the experience of individual users and when the experience is not satisfying, expose root causes with the precision of a specific line in source code.
Ivo Mägi
Co-founder and Head of Product, Plumbr

18. DIGITAL PERFORMANCE MANAGEMENT

Application Performance Management tools must evolve to become Digital Performance Management. As the definition of "application" is both expanding and becoming more vague, it's important for these tools to focus on the customer experience end-to-end. That's essentially what we mean by digital performance.
Jason Bloomberg
President, Intellyx

APM has historically been IT-centric, driven by operations and development, mainly to more efficiently identify and fix issues. However, this gives little or no thought to the digital customer experience. The most successful businesses are practicing what we call Digital Performance Management (DPM), using customer experience insights as a common language to foster collaboration and align priorities across these teams including business stakeholders. DPM collected analytics are uniquely positioned to help break silos by providing detailed insight around user behavior, delivered experience quality and the supporting applications and infrastructure health and performance across channels.
Erwan Paccard
Director of Customer Experience Marketing, Dynatrace

2016 will see the beginning of a mass transition from APM to DPM (Digital Performance Management) with emphasis on front-end performance measurement, testing and optimization based on analytics insights gained from the holy trinity of data - real user, business outcome and ops metrics.
Ann Ruckstuhl
CMO, SOASTA

19. APPLICATION-AWARE APM

The biggest evolution in application performance management will be application-aware solutions in the virtualized environment that tie the end user to the virtualized infrastructure that is delivering the application. As the management interface grows increasingly complex with virtual machines, hybrid cloud and hypervisor-based solutions, an evolution must take place to ensure that IT understands how their business critical applications are using compute, storage, network and virtualization resources on a user-by-user basis. As IT continues to evolve, monitoring solutions must also evolve to provide complete transparency throughout applications and all infrastructure layers.
Simon Taylor
President, Comtrade Software

Read 30 Ways APM Should Evolve - Part 5, covering the impact of APM on the Business.

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...