Skip to main content

John Rakowski from Forrester: 10 Must-Have APM Capabilities

During APMdigest's exclusive interview last month, John Rakowski, Forrester Analyst & Advisor Serving Infrastructure & Operations Professionals, outlined 10 must-have capabilities to look for when you are purchasing an Application Performance Management (APM) solution. Not included with the rest of the interview, here is the list published for the first time:

1. Simplicity

Complexity kills. Complexity in any monitoring solution is not going to provide value. So first and foremost any recommendation that I make is that simple is beautiful. Solutions must be simple to deploy quickly, simple to use, simple to access.

2. Collect All Data

APM solutions must be able to record data rapidly and store economically. You need to be able to record all data. It used to be that monitoring solutions would sample data every five minutes, or even every minute. That is too slow now. You need to be collecting all data.

3. Automation

APM solutions must automatically learn and understand what is important to the environment, in terms of the people, process and technology perspective. It is no good having the operator define this. Because of the rapid return you need to get from APM, these solutions need to be able to learn about the environment.

4. Integration

An APM solution is not going to be the only solution you invest in. A good monitoring approach is to have various products in a monitoring stack – infrastructure monitoring, network performance monitoring. So a good APM solution needs to be able to integrate easily with other monitoring solutions. An open API is a must here.

5. Single Source of the Truth

APM solutions must promote cooperation, and a single source of truth. Your APM solution must be a single source of truth for application performance and availability. And it is not just about traditional understanding of performance and availability. It is also about making sure that these applications are delivering the right customer experience.

6. Search

APM solutions should be collecting all data, so they must make it easy to search through that data.

7. Flexible Dashboards

APM solutions must make it easy to display information in context – whether it is to the business or IT. This requires the capability to easily create dashboards for multiple users.

8. Freemium Model

APM solutions must be available to try for free. I am a big advocate of the “freemium” model. For any APM solution, it is very hard to understand what value you are going to get from that solution in a trial period of 30 days.

9. Integration with Automation Solutions

Solutions must be able to trigger responses to situations rapidly, so integration with automation solutions is important.

10. Focus on Business

APM solutions must focus on business outcomes first, and technology second.

ABOUT John Rakowski

John Rakowski serves Infrastructure & Operations Professionals. He has eight years of experience in the technology and consulting industry, with certifications from Microsoft, VMware, Citrix, BMC, and the Information Technology Infrastructure Library (ITIL). At Forrester, his
research focuses on service management strategy, adoption, and implementation. In particular, Rakowski helps IT leaders and their teams understand the business value of service management, develop their strategy, evaluate and select vendor tools, and implement service management processes such as ITIL. Additionally, Rakowski focuses on the organizational impact of service management and its relationship to broader IT trends such as cloud computing.

Prior to joining Forrester in 2011, Rakowski was a solution architect for Fujitsu specializing in enterprise management. He has provided consultancy to a number of organizations in both the public and private sector and across different verticals ranging from the financial sector to not-for-profit charities. Some notable examples of his past clients are Deutsche Bank, Citigroup, KPMG, and Her Majesty’s Revenue and Customs (HMRC). He has also been a certified trainer delivering systems management courses on behalf of Microsoft. Working out of Forrester's London office, John holds a B.Sc. (Hons) in business information technology from Manchester Metropolitan University.

Hot Topics

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

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

John Rakowski from Forrester: 10 Must-Have APM Capabilities

During APMdigest's exclusive interview last month, John Rakowski, Forrester Analyst & Advisor Serving Infrastructure & Operations Professionals, outlined 10 must-have capabilities to look for when you are purchasing an Application Performance Management (APM) solution. Not included with the rest of the interview, here is the list published for the first time:

1. Simplicity

Complexity kills. Complexity in any monitoring solution is not going to provide value. So first and foremost any recommendation that I make is that simple is beautiful. Solutions must be simple to deploy quickly, simple to use, simple to access.

2. Collect All Data

APM solutions must be able to record data rapidly and store economically. You need to be able to record all data. It used to be that monitoring solutions would sample data every five minutes, or even every minute. That is too slow now. You need to be collecting all data.

3. Automation

APM solutions must automatically learn and understand what is important to the environment, in terms of the people, process and technology perspective. It is no good having the operator define this. Because of the rapid return you need to get from APM, these solutions need to be able to learn about the environment.

4. Integration

An APM solution is not going to be the only solution you invest in. A good monitoring approach is to have various products in a monitoring stack – infrastructure monitoring, network performance monitoring. So a good APM solution needs to be able to integrate easily with other monitoring solutions. An open API is a must here.

5. Single Source of the Truth

APM solutions must promote cooperation, and a single source of truth. Your APM solution must be a single source of truth for application performance and availability. And it is not just about traditional understanding of performance and availability. It is also about making sure that these applications are delivering the right customer experience.

6. Search

APM solutions should be collecting all data, so they must make it easy to search through that data.

7. Flexible Dashboards

APM solutions must make it easy to display information in context – whether it is to the business or IT. This requires the capability to easily create dashboards for multiple users.

8. Freemium Model

APM solutions must be available to try for free. I am a big advocate of the “freemium” model. For any APM solution, it is very hard to understand what value you are going to get from that solution in a trial period of 30 days.

9. Integration with Automation Solutions

Solutions must be able to trigger responses to situations rapidly, so integration with automation solutions is important.

10. Focus on Business

APM solutions must focus on business outcomes first, and technology second.

ABOUT John Rakowski

John Rakowski serves Infrastructure & Operations Professionals. He has eight years of experience in the technology and consulting industry, with certifications from Microsoft, VMware, Citrix, BMC, and the Information Technology Infrastructure Library (ITIL). At Forrester, his
research focuses on service management strategy, adoption, and implementation. In particular, Rakowski helps IT leaders and their teams understand the business value of service management, develop their strategy, evaluate and select vendor tools, and implement service management processes such as ITIL. Additionally, Rakowski focuses on the organizational impact of service management and its relationship to broader IT trends such as cloud computing.

Prior to joining Forrester in 2011, Rakowski was a solution architect for Fujitsu specializing in enterprise management. He has provided consultancy to a number of organizations in both the public and private sector and across different verticals ranging from the financial sector to not-for-profit charities. Some notable examples of his past clients are Deutsche Bank, Citigroup, KPMG, and Her Majesty’s Revenue and Customs (HMRC). He has also been a certified trainer delivering systems management courses on behalf of Microsoft. Working out of Forrester's London office, John holds a B.Sc. (Hons) in business information technology from Manchester Metropolitan University.

Hot Topics

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

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