Application Stability Management vs. Application Performance Management - Who Needs Them and Why
November 09, 2020

Leon Adato
SolarWinds

Share this

For IT teams, catching errors in applications before they become detrimental to a project is critical. Not only can it ensure that teams are not spending time going back and course correcting errors like transaction bottlenecks or application failures, but it can also save significant amounts of money if the problem becomes too far gone for it to be resolved quickly and efficiently. And wouldn't it be nice if there was someone standing over your shoulder, letting you know exactly when, where, and what the issue is so you can correct it immediately? Luckily, there are both application performance management (APM) and application stability management (ASM) solutions available that can do this for you, flagging errors in both the deployment and development stages of applications, before they can create larger issues down the line.

How Does It Work?

Tech teams often go back and forth on which solution makes the most sense for them to deploy, but the real answer is that because they monitor different aspects of an application, tech teams really stand to benefit from having both. It isn't a question of whether a team wants to invest in APM over ASM or vice versa — it's both, not an either or.

Applications are the oil that keeps the IT machine moving, so it's imperative that they are working their best at all times. And for the most part, organizations use APM to alert users about how their applications are performing in real time, as they are being used. One of the benefits of APM is it can be used to send alerts and flag errors to IT teams to let them know when an application may fail, allowing tech pros to fix applications before they can disrupt business. But ASM has a different functionality altogether and can assist developers when they are building applications to avoid errors in the development phase.

The development cycle can be unpredictable and full of surprises. With changes coming at any possible moment, developers rely on ASM to help them throughout the coding process and ensure there are no gaps in the code they are designing. With ASM, engineers aren't just coding the best they can and hoping for the best, but designing an application that has an almost flawless backbone so that APM solutions do not have to catch all of the problems. ASM can flag and trap new errors as they appear and allows developers to graph out the quality and severity of errors as they're produced. But even when an application is built with ASM, businesses need APM to ensure it's always performing optimally.

Unlike ASM that only catches errors in the development phase, APM can monitor and flag problems after an application has been executed and is in use. But it's worth noting that APM is never going to catch a problem that no one uses, making ASM all the more critical. Because ASM monitors code development, it can find problems that a user may never stumble across.

Making the Most of What You Have

The challenge with deciding when to use APM or ASM is that each option is catered for different teams. On the development side, APM doesn't provide the information they need to know about their code. Whereas for DevOps teams, monitoring engineers and more an APM solution provides the mature and complete overview to allow to know exactly what they are supposed to be getting.

For example, think about how most organizations have engineers on call. Some business leaders find this unnecessary, believing that if there were a problem you could simply kill the instance and reload a better version of the application. But from an engineer's perspective who primarily deals with containerized applications, they kill containers, and if there's a problem in their code, they automatically pull the previous known good version.

But when it comes to most tech pros, there's no real way to kill a router and then revert it from code if the router crashed, something that most engineers don't consider. Even though ASM and APM are definitely for coders and programmers, it's important to see how they are interconnected into the whole IT infrastructure and can impact the performance of what is happening beyond the applications.

But perhaps the most important to remember is that all of these pieces matter holistically and should be interconnected with each other. If you have an APM or ASM tool that stands alone and can't incorporate the different metrics and data, then the tools will only ever be used as a point solution. For the most impactful information, they should operate together.

Leon Adato is a Head Geek at SolarWinds
Share this

The Latest

February 25, 2021

Organizations use data to fuel their operations, make smart business decisions, improve customer relationships, and much more. Because so much value can be extracted from data its influence is generally positive, but it can also be detrimental to a business experiencing a serious disruption such as a cyberattack, insider threat, or storage platform-specific hack or bug ...

February 24, 2021

Previously siloed IT teams and technologies are converging as enterprises accelerate their modernization efforts in reaction to COVID-19, according to a study by LogicMonitor ...

February 23, 2021

You surf the internet, don't you? While all of us are at home due to Covid lock-down and accepting a new reality, the majority of the work is happening online. IT managers are looking for tools that can track the user digital experience. Executives are reading a report from Gartner or Forrester about some of the best networking monitoring solutions available on the market. Project managers are using Microsoft Teams online to communicate and ensure team members are meeting deliverables on time. Remote employees everywhere use OWA to check their office mails. No matter what, you can be quite sure that everyone is using their favorite browser and search engine for connecting online and accomplish tasks ...

February 22, 2021

With the right solutions, teams can move themselves out of the shadows of error resolution and into the light of innovation. Observability data, drawn from their systems and imbued with context from AI, lets teams automate the issues holding them back. Contextualized data and insights also give them the language to speak to the incremental, product-led approach and the direction to drive key innovations in customer experience improvement. Communicating value becomes a much easier proposition for DevOps practitioners — and they can take their seat at the company table as contributors to value ...

February 18, 2021

Prediction: Successful organizations will blur (or erase) the line between ITOps and DevOps. DevOps has to coexist with traditional IT operations ... So bring a little DevOps to every aspect of IT operations. You don't even have to call it DevOps ...

February 17, 2021

The use of unified communications and collaboration (UC&C) solutions has increased since the start of the pandemic, and this increased use has created challenges for IT teams, according to a survey commissioned by NETSCOUT SYSTEMS ...

February 16, 2021
The AI+ITOPS Podcast just hit the 10K + download mark early this month. Most people listen to entire episodes, and many engage with us by sending a note on LinkedIn, Twitter, a direct email asking questions, clarifications, strategy advice, product selection advice ...
February 11, 2021

Cloud-based innovations like microservices, containers and orchestration let developers code better, faster, but the underlying infrastructure becomes dynamic and ephemeral, and service-level interactions are hard to see. It’s a critical evolution, but the rapid change reduces visibility, predictability and control. Hence, observability ...

February 10, 2021

Companies love data. Aggregating data from multiple sources makes decision-making easier and brings a new depth of the conversation to business meetings. But all of this is at the management level. IT managers and administrators also search for data from multiple sources to ensure that the ecosystem works ...

February 09, 2021

The cost of poor software quality (CPSQ) in the US in 2020 was approximately $2.08 trillion, according to The Cost of Poor Software Quality In the US: A 2020 Report from the Consortium for Information & Software Quality (CISQ), co-sponsored by Synopsys. This includes poor software quality resulting from software failures, unsuccessful development projects, legacy system problems, technical debt and cybercrime enabled by exploitable weaknesses and vulnerabilities in software ...