The Case for Application Experience Monitoring

Why ‘"app assurance" is just as (or more) important than APM
Andrew Marshall

For today's software development teams, application performance monitoring (APM) is a fairly ubiquitous technology and an effective tool to monitor how applications are performing in production. The functionality of APM has evolved since it arrived on the scene in the late 90s, with several vendors building monitoring functionality that works well with distributed (i.e. not monolithic) applications. Despite these advances, APM remains at its core a mechanism for Dev teams to track how an application is working at the code and transaction level.

All the customer cares about is how they are enjoying an app.

While this is still useful, it doesn't address the ultimate goal of DevOps teams: to deliver the desired application experience to end users. Code working perfectly doesn't matter much if apps aren't reaching customers, or are negatively impacted by network latency or outages. All the customer cares about is how they are enjoying an app. To effectively guarantee application availability and usage satisfaction, DevOps teams need to leverage three important application assurance data sets into their delivery automation logic:

■ Application user experience: Real User Monitoring (RUM)

■ Real-time infrastructure health status: Synthetic testing

■ IT tool data feeds: Key IT health data like (traditional) APM, local load balancer (LOB) data and cloud metrics

Application User Experience: Real User Monitoring (RUM)

When is an app truly "green"? Answer: when it's working correctly for end users. Real user monitoring (RUM) allows Ops teams to fully understanding how internet performance impacts customer satisfaction and engagement. No matter where an app is hosted — in clouds, data centers, or CDNs — Ops teams need to make sure delivery of these apps looks good from the user perspective. RUM gives teams a real-time understanding of worldwide network health, which in turn delivers the performance data needed to automate app delivery, and ensure the best user experience your application can offer. An end user-centric approach to application assurance is critical to Application Experience Monitoring.

Real-Time Infrastructure Health Status: Synthetic Testing

Modern infrastructure is dynamic, distributed, and heterogeneous in nature. When your delivery architecture is comprised of one or more clouds, data centers, or CDNs, understanding the status of your infrastructure becomes a difficult proposition. It's critical that you test all of your endpoints: in your public clouds, private clouds, data centers, or CDNs. This provides a comprehensive and uniform view of the overall health of your applications delivery, no matter what the status of your various infrastructure components happens to be.

Synthetic testing acts like a virtual end point, testing the throughput of an application, video, or large file download. Being able to test your app from remote locations worldwide helps ensure your data has incredibly low latency, and therefore is actually usable for your app delivery strategy. Healthy infrastructure makes for deliverable apps.

IT Tool Data Feeds

As mentioned, a basic understanding of how an app is performing at the code and transaction level (i.e. traditional APM) is still important. This monitoring data is a key part of the third aspect of application assurance that DevOps teams need to leverage in addition to RUM and infrastructure health: IT Tool Data Feeds. There are various other monitoring and real-time metrics available to IT Ops to help them automate app delivery with the most robust set of data. (Traditional) APM is certainly one of these. Understanding the health of the app code is obviously still useful for making real-time delivery decisions in your software-defined app delivery platform.

On top of that there are many other data sources to leverage, of course, such as: local load balancer (i.e. NGINX, HAProxy) health metrics, cloud status metrics (i.e. AWS Cloudwatch), etc. These are just a few examples. Chances are your business collects data from LOB apps or other mission-critical services that are instrumental to your IT organization. These are tools you're paying (or paid) for, so you should use them for your application delivery automation if they're accessible. They're just as important as traditional APM.

DevOps Requires Insight + Action

DevOps teams are under constant pressure to support continuous deployment, agile methodology, and an acceptable uptime for applications. "Monitoring" isn't a solution, but actually just a way to collect data. Ops teams then use this data to make sure apps are delivered to customers with an optimal experience in mind. When both dev and ops teams have a single lens to view IT health data (from the three sources above) and a set of application delivery rules, they can react quickly to changes in these data feeds to assure the one thing that matters: the application experience by end users. Application Experience Monitoring as a practice helps make this possible.

Once DevOps teams understand how the Application Experience impacts global customers, the next important step is to do something with that information. That's where a software-defined application delivery platform comes in. Leveraging this powerful data set to automate application, video, and website delivery allows Ops teams to "self-heal" when network outages or latency issues happen. Insight plus action is the next step for APM.

Related Links

Hot Topics

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

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

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

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

The Case for Application Experience Monitoring

Why ‘"app assurance" is just as (or more) important than APM
Andrew Marshall

For today's software development teams, application performance monitoring (APM) is a fairly ubiquitous technology and an effective tool to monitor how applications are performing in production. The functionality of APM has evolved since it arrived on the scene in the late 90s, with several vendors building monitoring functionality that works well with distributed (i.e. not monolithic) applications. Despite these advances, APM remains at its core a mechanism for Dev teams to track how an application is working at the code and transaction level.

All the customer cares about is how they are enjoying an app.

While this is still useful, it doesn't address the ultimate goal of DevOps teams: to deliver the desired application experience to end users. Code working perfectly doesn't matter much if apps aren't reaching customers, or are negatively impacted by network latency or outages. All the customer cares about is how they are enjoying an app. To effectively guarantee application availability and usage satisfaction, DevOps teams need to leverage three important application assurance data sets into their delivery automation logic:

■ Application user experience: Real User Monitoring (RUM)

■ Real-time infrastructure health status: Synthetic testing

■ IT tool data feeds: Key IT health data like (traditional) APM, local load balancer (LOB) data and cloud metrics

Application User Experience: Real User Monitoring (RUM)

When is an app truly "green"? Answer: when it's working correctly for end users. Real user monitoring (RUM) allows Ops teams to fully understanding how internet performance impacts customer satisfaction and engagement. No matter where an app is hosted — in clouds, data centers, or CDNs — Ops teams need to make sure delivery of these apps looks good from the user perspective. RUM gives teams a real-time understanding of worldwide network health, which in turn delivers the performance data needed to automate app delivery, and ensure the best user experience your application can offer. An end user-centric approach to application assurance is critical to Application Experience Monitoring.

Real-Time Infrastructure Health Status: Synthetic Testing

Modern infrastructure is dynamic, distributed, and heterogeneous in nature. When your delivery architecture is comprised of one or more clouds, data centers, or CDNs, understanding the status of your infrastructure becomes a difficult proposition. It's critical that you test all of your endpoints: in your public clouds, private clouds, data centers, or CDNs. This provides a comprehensive and uniform view of the overall health of your applications delivery, no matter what the status of your various infrastructure components happens to be.

Synthetic testing acts like a virtual end point, testing the throughput of an application, video, or large file download. Being able to test your app from remote locations worldwide helps ensure your data has incredibly low latency, and therefore is actually usable for your app delivery strategy. Healthy infrastructure makes for deliverable apps.

IT Tool Data Feeds

As mentioned, a basic understanding of how an app is performing at the code and transaction level (i.e. traditional APM) is still important. This monitoring data is a key part of the third aspect of application assurance that DevOps teams need to leverage in addition to RUM and infrastructure health: IT Tool Data Feeds. There are various other monitoring and real-time metrics available to IT Ops to help them automate app delivery with the most robust set of data. (Traditional) APM is certainly one of these. Understanding the health of the app code is obviously still useful for making real-time delivery decisions in your software-defined app delivery platform.

On top of that there are many other data sources to leverage, of course, such as: local load balancer (i.e. NGINX, HAProxy) health metrics, cloud status metrics (i.e. AWS Cloudwatch), etc. These are just a few examples. Chances are your business collects data from LOB apps or other mission-critical services that are instrumental to your IT organization. These are tools you're paying (or paid) for, so you should use them for your application delivery automation if they're accessible. They're just as important as traditional APM.

DevOps Requires Insight + Action

DevOps teams are under constant pressure to support continuous deployment, agile methodology, and an acceptable uptime for applications. "Monitoring" isn't a solution, but actually just a way to collect data. Ops teams then use this data to make sure apps are delivered to customers with an optimal experience in mind. When both dev and ops teams have a single lens to view IT health data (from the three sources above) and a set of application delivery rules, they can react quickly to changes in these data feeds to assure the one thing that matters: the application experience by end users. Application Experience Monitoring as a practice helps make this possible.

Once DevOps teams understand how the Application Experience impacts global customers, the next important step is to do something with that information. That's where a software-defined application delivery platform comes in. Leveraging this powerful data set to automate application, video, and website delivery allows Ops teams to "self-heal" when network outages or latency issues happen. Insight plus action is the next step for APM.

Related Links

Hot Topics

The Latest

Keys to Building a Partner Ecosystem That Scales

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

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

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

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