Skip to main content

Application Performance Monitoring Cheat Sheet

Phee-Lip
BHP

A brief introduction to Applications Performance Monitoring (APM), breaking it down to a few key points:

1. It is different from conventional infrastructure monitoring which primarily captures and reports on hardware performance such as CPU and memory but APM also covers more advanced infra technology, such as containers, etc.

2. APM tells you how the application, which sits on top of the infrastructure, is performing by going deep into the code level and it includes the capability to monitor microservices and different types of programming languages.

3. Recently (actually not so recent) it has expanded to include user experience monitoring which encapsulates capturing of the user journey, reporting of errors and performance of user-triggered activities (click-on-page) as user behavior and experience are becoming more essential.

4. With a huge amount of data being collected, it is only natural that it has become a big data platform for companies to gain insights into their operations and business. Hence the expansion into analytic!

A few important lessons which I have learned over the years:

1. Many organizations are still "stuck" at reporting service availability. This requires a fundamental mindset change as the spotlight is now on application performance and service quality. These are critical aspects of digitization which no companies can afford to neglect.

2. APM can pinpoint the problems but it can't fix them for you. At least not now, perhaps later with AI. It is not a silver bullet and it draws out a very important point that organizations MUST HAVE system/domain expertise to maintain and improve the systems which are the most critical to their business!

3. Not everything is created equally. Hence you don't need a full-fledged APM tool for every system. Focus on the most critical systems. That will not only save you money but enable you to have undivided attention only on those which you care deeply about.

4. It is hard to find the best APM tool in every aspect of its capabilities. You just have to decide what are the most crucial elements for success and find the best solutions for them. You may end up with a couple of tools, hence it will be good to look at how you can gain a cohesive view across these tools to form your master service performance dashboard. Some form of integration may be required.

5. Many organizations have a central monitoring team who have eyes-on monitoring 24x7. This is old school and ineffective. Natural language processing (NLP) is the future with exception-based voice notification and an intelligent contextual query to have a deep understanding of systems health and performance, anytime, anywhere.

APM is a complex topic as it is a multi-faceted discipline. It will continue to evolve, branching into other domains such as service automation (self-healing), service management and deep learning. These areas have been coined as AIOps by Gartner, heavily anchored on AI. Definitely a space to watch out going forward!

Phee-Lip is Principal, APM Practice Lead, at BHP

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

Application Performance Monitoring Cheat Sheet

Phee-Lip
BHP

A brief introduction to Applications Performance Monitoring (APM), breaking it down to a few key points:

1. It is different from conventional infrastructure monitoring which primarily captures and reports on hardware performance such as CPU and memory but APM also covers more advanced infra technology, such as containers, etc.

2. APM tells you how the application, which sits on top of the infrastructure, is performing by going deep into the code level and it includes the capability to monitor microservices and different types of programming languages.

3. Recently (actually not so recent) it has expanded to include user experience monitoring which encapsulates capturing of the user journey, reporting of errors and performance of user-triggered activities (click-on-page) as user behavior and experience are becoming more essential.

4. With a huge amount of data being collected, it is only natural that it has become a big data platform for companies to gain insights into their operations and business. Hence the expansion into analytic!

A few important lessons which I have learned over the years:

1. Many organizations are still "stuck" at reporting service availability. This requires a fundamental mindset change as the spotlight is now on application performance and service quality. These are critical aspects of digitization which no companies can afford to neglect.

2. APM can pinpoint the problems but it can't fix them for you. At least not now, perhaps later with AI. It is not a silver bullet and it draws out a very important point that organizations MUST HAVE system/domain expertise to maintain and improve the systems which are the most critical to their business!

3. Not everything is created equally. Hence you don't need a full-fledged APM tool for every system. Focus on the most critical systems. That will not only save you money but enable you to have undivided attention only on those which you care deeply about.

4. It is hard to find the best APM tool in every aspect of its capabilities. You just have to decide what are the most crucial elements for success and find the best solutions for them. You may end up with a couple of tools, hence it will be good to look at how you can gain a cohesive view across these tools to form your master service performance dashboard. Some form of integration may be required.

5. Many organizations have a central monitoring team who have eyes-on monitoring 24x7. This is old school and ineffective. Natural language processing (NLP) is the future with exception-based voice notification and an intelligent contextual query to have a deep understanding of systems health and performance, anytime, anywhere.

APM is a complex topic as it is a multi-faceted discipline. It will continue to evolve, branching into other domains such as service automation (self-healing), service management and deep learning. These areas have been coined as AIOps by Gartner, heavily anchored on AI. Definitely a space to watch out going forward!

Phee-Lip is Principal, APM Practice Lead, at BHP

Hot Topics

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...