Skip to main content

Gartner Q&A: Jonah Kowall Talks About APM - Part 2

Pete Goldin
APMdigest

In Part 2 of APMdigest's exclusive interview, Jonah Kowall, Research Vice President, IT Operations Management at Gartner, discusses Gartner's 2013 Magic Quadrant for Application Performance Monitoring (APM), complexity in today's product offerings, and the market's move to simplify APM.

Start with Part 1 of the interview

APM: In Gartner's 2013 Magic Quadrant for APM, complexity seems to be cited as a caution for many vendors.

JK: This also goes back to Software-as-a-Service (SaaS). If you simplify deployment, and you simplify the administration, that helps the complexity problem.

The other piece is obviously the usability of the product itself. A lot of these products require multiple user interfaces, multiple tools, especially when you look at some of the legacy solutions. That manifests itself in usability complexity, which limits who can use them, how they use the data, and the training required to get value from the solution.

Vendors keep adding too many features, and too many functions, far too many knobs and dials to all of these solutions. They listen to customer requests without considering the impact the requests have on the potential buyers or the broader customer base. This results in users being overwhelmed, and users having to become experts in order to use these tools, which is not ideal, of course.

Another piece that affects complexity is the use of analytics. How can the solution coach the user to go down a path to accomplish what they want to do? That is a combination of analyzing the data that is coming into the solution and also being able to learn what users typically do in the workflows. That can simplify how much time it takes the user to get the answer they are looking for. Analytics tools often present data or answer simplified questions versus providing insight and moving a tool towards being proactive.

APM: Yet the report says you expect the product offerings to be simplified by the end of 2014 - to a point where only vendors who have simplified APM will be competitive. Does this mean all these vendors are aggressively overhauling and simplifying their portfolios right now?

JK: Yes, almost every vendor is making simplicity one of the key goals in terms of redesigns and revamps of their APM tools, from the big vendors to many of the smaller vendors that had this mantra from the beginning. Those players with a focus on usability and simplicity have been taking market share, this makes everyone pay attention and emulate.

Some vendors had to change gears because of what is happening in the market. They realize that people want simple straightforward tools that don't have 100% of the functionality but can accomplish the basic needs for less money with less complexity. That is clearly what we are seeing happen, not just in APM but in monitoring as a whole.

I would say simplicity is not the norm today, but when you look at priorities across the well-established players in the market, simplicity is definitely something that they are all striving towards.

APM: What do you see as the greatest weakness of the APM market? What are the vendors missing?

JK: Buyers would like to have one monitoring tool. And that does not mean five tools that are integrated together – that means one tool.

Today, monitoring is divided into two categories: availability and performance. First, there is a lot of availability monitoring that happens, whether it is ensuring that the infrastructure is functional, or doing synthetic testing to make sure the application is functional. Then APM is obviously on the performance side. There is the whole performance element, whether it is APM or Network Performance Management (NPM) looking at the network, or the applications, and the performance and the latency in the actual application execution. Enterprises want to buy availability and performance tools together, meaning one tool, but it does not exist today. That is definitely where vendors are missing the mark.

APM: Why do you think this is happening?

JK: Part of the issue is, if someone raises venture capital today to start a new company and solve the biggest problems, they would use that money to build an APM product rather than build an availability product. All the new companies out there innovating tend to be in the APM space because there is still innovation that needs to happen there as applications continue to change drastically.

The availability space is mostly commoditized, however, and no one has really disrupted it, from a technology perspective. This proliferates the problem, these small specialist vendors get bought by large vendors that offer multiple tools, and then they become yet another tool that needs to plug into a broader portfolio of technologies.

I think the biggest point that is being missed by the larger vendors is this idea of a single tool that can do multiple tasks. That is clearly what users want, it just does not exist. Users have to buy at least two, if not more, different tools today.

APM: There are companies that offer both availability and performance tools, or APM and NPM tools for example, but you are saying they need to put them together in one unified tool?

JK: One single product, versus being part of a suite. A vendor might have specific tools that do availability of the network, the servers. Some vendors have storage tools, and virtualization tools, and then they also offer APM tools that are separate. Some of them even offer NPM tools that are separate. They may offer a console that rolls up information or alerts from all their tools. But generally speaking these are all separate tools from separate acquisitions that work differently, look different, the technologies are all completely different.

When a user implements a suite of these tools to cover monitoring, they have to deal with about five or six different technologies with different databases, different platforms, and different UIs. It becomes very complex and difficult to manage. That is why users are rebelling against that large suite of tools, because they just don't have time to manage and maintain it. It is not a good use of time.

APM: Speaking of NPM, in your 2014 Magic Quadrant for Network Performance Monitoring and Diagnostics (NPMD), released in March, you consider it a strength to offer both APM and NPMD together. Do you foresee these tools becoming more integrated?

JK: APM and NPMD target different buyers. Today, the needs of the network professional are different from the needs of APM buyers. If Software-Defined Networking (SDN) continues to evolve, and the network team starts to merge with other groups in the organization, and is no longer considered a silo – as it is today in almost every organization – then I think the tools will follow suit. But today there are clearly different buyers for these tools, for different use cases with different expectations.

Gartner Q&A: Jonah Kowall Talks About APM - Part 3

In Part 3, Jonah Kowall discusses the changing and volatile APM market in 2014 and beyond.

Related Links:

Gartner Q&A: Jonah Kowall Talks About APM - Part 1

Hot Topic
The Latest
The Latest 10

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

Gartner Q&A: Jonah Kowall Talks About APM - Part 2

Pete Goldin
APMdigest

In Part 2 of APMdigest's exclusive interview, Jonah Kowall, Research Vice President, IT Operations Management at Gartner, discusses Gartner's 2013 Magic Quadrant for Application Performance Monitoring (APM), complexity in today's product offerings, and the market's move to simplify APM.

Start with Part 1 of the interview

APM: In Gartner's 2013 Magic Quadrant for APM, complexity seems to be cited as a caution for many vendors.

JK: This also goes back to Software-as-a-Service (SaaS). If you simplify deployment, and you simplify the administration, that helps the complexity problem.

The other piece is obviously the usability of the product itself. A lot of these products require multiple user interfaces, multiple tools, especially when you look at some of the legacy solutions. That manifests itself in usability complexity, which limits who can use them, how they use the data, and the training required to get value from the solution.

Vendors keep adding too many features, and too many functions, far too many knobs and dials to all of these solutions. They listen to customer requests without considering the impact the requests have on the potential buyers or the broader customer base. This results in users being overwhelmed, and users having to become experts in order to use these tools, which is not ideal, of course.

Another piece that affects complexity is the use of analytics. How can the solution coach the user to go down a path to accomplish what they want to do? That is a combination of analyzing the data that is coming into the solution and also being able to learn what users typically do in the workflows. That can simplify how much time it takes the user to get the answer they are looking for. Analytics tools often present data or answer simplified questions versus providing insight and moving a tool towards being proactive.

APM: Yet the report says you expect the product offerings to be simplified by the end of 2014 - to a point where only vendors who have simplified APM will be competitive. Does this mean all these vendors are aggressively overhauling and simplifying their portfolios right now?

JK: Yes, almost every vendor is making simplicity one of the key goals in terms of redesigns and revamps of their APM tools, from the big vendors to many of the smaller vendors that had this mantra from the beginning. Those players with a focus on usability and simplicity have been taking market share, this makes everyone pay attention and emulate.

Some vendors had to change gears because of what is happening in the market. They realize that people want simple straightforward tools that don't have 100% of the functionality but can accomplish the basic needs for less money with less complexity. That is clearly what we are seeing happen, not just in APM but in monitoring as a whole.

I would say simplicity is not the norm today, but when you look at priorities across the well-established players in the market, simplicity is definitely something that they are all striving towards.

APM: What do you see as the greatest weakness of the APM market? What are the vendors missing?

JK: Buyers would like to have one monitoring tool. And that does not mean five tools that are integrated together – that means one tool.

Today, monitoring is divided into two categories: availability and performance. First, there is a lot of availability monitoring that happens, whether it is ensuring that the infrastructure is functional, or doing synthetic testing to make sure the application is functional. Then APM is obviously on the performance side. There is the whole performance element, whether it is APM or Network Performance Management (NPM) looking at the network, or the applications, and the performance and the latency in the actual application execution. Enterprises want to buy availability and performance tools together, meaning one tool, but it does not exist today. That is definitely where vendors are missing the mark.

APM: Why do you think this is happening?

JK: Part of the issue is, if someone raises venture capital today to start a new company and solve the biggest problems, they would use that money to build an APM product rather than build an availability product. All the new companies out there innovating tend to be in the APM space because there is still innovation that needs to happen there as applications continue to change drastically.

The availability space is mostly commoditized, however, and no one has really disrupted it, from a technology perspective. This proliferates the problem, these small specialist vendors get bought by large vendors that offer multiple tools, and then they become yet another tool that needs to plug into a broader portfolio of technologies.

I think the biggest point that is being missed by the larger vendors is this idea of a single tool that can do multiple tasks. That is clearly what users want, it just does not exist. Users have to buy at least two, if not more, different tools today.

APM: There are companies that offer both availability and performance tools, or APM and NPM tools for example, but you are saying they need to put them together in one unified tool?

JK: One single product, versus being part of a suite. A vendor might have specific tools that do availability of the network, the servers. Some vendors have storage tools, and virtualization tools, and then they also offer APM tools that are separate. Some of them even offer NPM tools that are separate. They may offer a console that rolls up information or alerts from all their tools. But generally speaking these are all separate tools from separate acquisitions that work differently, look different, the technologies are all completely different.

When a user implements a suite of these tools to cover monitoring, they have to deal with about five or six different technologies with different databases, different platforms, and different UIs. It becomes very complex and difficult to manage. That is why users are rebelling against that large suite of tools, because they just don't have time to manage and maintain it. It is not a good use of time.

APM: Speaking of NPM, in your 2014 Magic Quadrant for Network Performance Monitoring and Diagnostics (NPMD), released in March, you consider it a strength to offer both APM and NPMD together. Do you foresee these tools becoming more integrated?

JK: APM and NPMD target different buyers. Today, the needs of the network professional are different from the needs of APM buyers. If Software-Defined Networking (SDN) continues to evolve, and the network team starts to merge with other groups in the organization, and is no longer considered a silo – as it is today in almost every organization – then I think the tools will follow suit. But today there are clearly different buyers for these tools, for different use cases with different expectations.

Gartner Q&A: Jonah Kowall Talks About APM - Part 3

In Part 3, Jonah Kowall discusses the changing and volatile APM market in 2014 and beyond.

Related Links:

Gartner Q&A: Jonah Kowall Talks About APM - Part 1

Hot Topic
The Latest
The Latest 10

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...