Skip to main content

APM and Application Stability: Where Two Monitoring Roads Merge and Diverge - Part 2

James Smith
SmartBear

In today's iterative world, development teams care a lot more about how apps are running. There's a demand for fixing actionable items. Developers want to know exactly what's broken, what to fix right now, and what can wait. They want to know, "Do we build or fix?" This trade-off between building new features versus fixing bugs is one of the key factors behind the adoption of Application Stability management tools.

Start with APM and Application Stability: Where Two Monitoring Roads Merge and Diverge - Part 1

Benefits of Application Stability

The beauty of Application Stability is that it brings together the errors captured by APM and enables developers to see at a glance which ones are worth fixing. As a result, five major benefits arise:

1. Increased efficiency: Companies eliminate the problem of infrastructure teams tossing issues over the fence to development teams. Valuable time is saved because Application Stability tools remove the game of telephone between the two teams and deliver bugs directly to the team that will fix them.

2. Stronger CSAT: The time to fix bugs goes down dramatically when the person who wrote the code fixes the code. With diagnostic information in hand from the Application Stability tool, software engineers innately understand what the code does, what the bug means, and how to fix it. Faster resolution of bugs that impact the end user experience means that customer satisfaction levels (CSAT) are less likely to drop.

3. Error prioritization: Application Stability tools group bugs by root cause, making it easy for developers to get a sense of severity at a glance. It's much easier to determine what to fix first when developers can see which errors are most costly, which affect the most customers, and which bug is impacting a key customer.

4. Tool synchronization: Taking it one step further, Application Stability tools are tied into project management suites. Bugs map directly to tickets created in Jira (or whatever tool is used), and tickets update automatically as priority changes.

5. Stability scores by release: Application Stability enables product and development teams to see stability scores by release. Since it's common to have multiple app versions live at the same time, especially with mobile apps (where DevOps isn't really involved), companies can't rely on a single stability score. Teams need to see stability by release so that it's clear exactly where the errors are and what impact they're having on users.

What Percentage of Your Development Team Has a Login to Your APM?

I'm often asked whether I think Application Stability will replace APM, and my answer is simple: No, I don't

I'm often asked whether I think Application Stability will replace APM, and my answer is simple: No, I don't. APM remains an essential part of developing software, and organizations still need to understand when they're about to run out of resources and when there's poor performance. 

Instead, I see these two solutions co-existing as adjacent categories but helping different teams. Application Stability delivers prioritized errors to developers for fixing, while APM works well for enabling Ops teams to raise red flags on high error rates and reduce cloud spend.

Some of you may be thinking to yourself, "Well, my APM product does what you're describing for application stability, so I'm sure my developers are fine using it."

To which I poise the following challenge: What percentage of your dev team has a login to your APM? What percentage logs in on a daily basis? And, if they do use it, do your developers like it?

The answers to these questions may surprise you. After all, APM wasn't really built for developers or for keeping end users happy. In contrast, Application Stability was born at the customer layer and is designed specifically to monitor the front end and ensure strong customer experiences with web and mobile apps.

Once you've had a chance to hear from your dev team, it wouldn't surprise me if you discover that they're pretty excited about the new kid in town.

James Smith is SVP of the Bugsnag Product Group at SmartBear

Hot Topics

The Latest

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

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...

Seamless shopping is a basic demand of today's boundaryless consumer — one with little patience for friction, limited tolerance for disconnected experiences and minimal hesitation in switching brands. Customers expect intuitive, highly personalized experiences and the ability to move effortlessly across physical and digital channels within the same journey. Failure to deliver can cost dearly ...

If your best engineers spend their days sorting tickets and resetting access, you are wasting talent. New global data shows that employees in the IT sector rank among the least motivated across industries. They're under a lot of pressure from many angles. Pressure to upskill and uncertainty around what agentic AI means for job security is creating anxiety. Meanwhile, these roles often function like an on-call job and require many repetitive tasks ...

APM and Application Stability: Where Two Monitoring Roads Merge and Diverge - Part 2

James Smith
SmartBear

In today's iterative world, development teams care a lot more about how apps are running. There's a demand for fixing actionable items. Developers want to know exactly what's broken, what to fix right now, and what can wait. They want to know, "Do we build or fix?" This trade-off between building new features versus fixing bugs is one of the key factors behind the adoption of Application Stability management tools.

Start with APM and Application Stability: Where Two Monitoring Roads Merge and Diverge - Part 1

Benefits of Application Stability

The beauty of Application Stability is that it brings together the errors captured by APM and enables developers to see at a glance which ones are worth fixing. As a result, five major benefits arise:

1. Increased efficiency: Companies eliminate the problem of infrastructure teams tossing issues over the fence to development teams. Valuable time is saved because Application Stability tools remove the game of telephone between the two teams and deliver bugs directly to the team that will fix them.

2. Stronger CSAT: The time to fix bugs goes down dramatically when the person who wrote the code fixes the code. With diagnostic information in hand from the Application Stability tool, software engineers innately understand what the code does, what the bug means, and how to fix it. Faster resolution of bugs that impact the end user experience means that customer satisfaction levels (CSAT) are less likely to drop.

3. Error prioritization: Application Stability tools group bugs by root cause, making it easy for developers to get a sense of severity at a glance. It's much easier to determine what to fix first when developers can see which errors are most costly, which affect the most customers, and which bug is impacting a key customer.

4. Tool synchronization: Taking it one step further, Application Stability tools are tied into project management suites. Bugs map directly to tickets created in Jira (or whatever tool is used), and tickets update automatically as priority changes.

5. Stability scores by release: Application Stability enables product and development teams to see stability scores by release. Since it's common to have multiple app versions live at the same time, especially with mobile apps (where DevOps isn't really involved), companies can't rely on a single stability score. Teams need to see stability by release so that it's clear exactly where the errors are and what impact they're having on users.

What Percentage of Your Development Team Has a Login to Your APM?

I'm often asked whether I think Application Stability will replace APM, and my answer is simple: No, I don't

I'm often asked whether I think Application Stability will replace APM, and my answer is simple: No, I don't. APM remains an essential part of developing software, and organizations still need to understand when they're about to run out of resources and when there's poor performance. 

Instead, I see these two solutions co-existing as adjacent categories but helping different teams. Application Stability delivers prioritized errors to developers for fixing, while APM works well for enabling Ops teams to raise red flags on high error rates and reduce cloud spend.

Some of you may be thinking to yourself, "Well, my APM product does what you're describing for application stability, so I'm sure my developers are fine using it."

To which I poise the following challenge: What percentage of your dev team has a login to your APM? What percentage logs in on a daily basis? And, if they do use it, do your developers like it?

The answers to these questions may surprise you. After all, APM wasn't really built for developers or for keeping end users happy. In contrast, Application Stability was born at the customer layer and is designed specifically to monitor the front end and ensure strong customer experiences with web and mobile apps.

Once you've had a chance to hear from your dev team, it wouldn't surprise me if you discover that they're pretty excited about the new kid in town.

James Smith is SVP of the Bugsnag Product Group at SmartBear

Hot Topics

The Latest

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

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...

Seamless shopping is a basic demand of today's boundaryless consumer — one with little patience for friction, limited tolerance for disconnected experiences and minimal hesitation in switching brands. Customers expect intuitive, highly personalized experiences and the ability to move effortlessly across physical and digital channels within the same journey. Failure to deliver can cost dearly ...

If your best engineers spend their days sorting tickets and resetting access, you are wasting talent. New global data shows that employees in the IT sector rank among the least motivated across industries. They're under a lot of pressure from many angles. Pressure to upskill and uncertainty around what agentic AI means for job security is creating anxiety. Meanwhile, these roles often function like an on-call job and require many repetitive tasks ...