Skip to main content

Franken-Monitoring - A Case of Too Many Tools

Most Organizations Have 11 or more tools to Manage Application Performance
Kalyan Ramanathan

In a recent interview, an IT operations director told us, “We frankly have too many tools, and many of them weren’t performing to our expectations.”

If you are an enterprise ops leader managing complex applications, you can probably relate to that statement. At AppDynamics, we call this “Franken-monitoring,” a situation characterized by many, usually too many, siloed tools — for application, server, database, end-user client, etc. — that provide varying levels of disparate visibility into IT applications.

The challenges with this approach include:

■ Tools have minimal integration or common context, which makes it near impossible to manage the application or its business transactions.

■ Tools are designed for subject-matter experts, so it’s hard to provide value to the ops team as a whole.

■ Tools have high total cost of ownership, since every tool has to be independently procured, installed and managed, and staff have to be trained in their use.

2015 APM Tools Survey Finds That Tools Are Underutilized and Solving Performance Problems is Still a Massive Challenge

We commissioned analyst firm Enterprise Management Associates (EMA) to get to the bottom of this. In the 2015 APM Tools Survey, EMA found that a majority of surveyed enterprises have 11 or more commercial tools in their arsenal to manage application performance.

Nearly two-thirds of respondents report that it takes at least three hours to determine the root cause of performance issues; one-third report that it takes six or more hours to find the source of an issue.

EMA’s survey indicated that the lack of application-focused solutions appears to contribute to current IT challenges, with IT teams often trying to manage modern, complex applications with siloed tools and primarily manual processes. Just about every user of monitoring tools complains about the challenges of having too many tools without any situational awareness. Current approaches to integrate these tools with solutions like MoM (manager of managers) or CMDB (configuration management database) have for the most part failed, because it is hard to stitch together these disparate solutions from different vendors.

Gartner recently did a survey that pointed exactly to this challenge. The key reasons (besides price) for poor APM adoption were, indeed, the complexity of the tools and poor integration between tools.

Specifically, the EMA study found:

■ Siloed and shelved monitoring tools: 65 percent of the companies surveyed indicated that they own more than 10 different commercial monitoring products. Nearly half also indicated that 50 percent or fewer of their purchased tools are actively being used.

■ Manual resources expended on application support: According to respondents, calls from users are the second-most frequent way IT organizations find out about application-related problems (27 percent cited detection by monitoring centers; 25 percent cited user calls). Line staff, those closest to the problem, report a significantly higher incidence, citing user calls as their first “heads up” 35 percent of the time.

■ Extensive people-hours required to solve a single application problem: IT organizations surveyed indicated that, for those application-related problems escalated beyond Level 1 support, mean time to repair (MTTR) is most often between five and seven hours; in addition, between three and four people are typically required to solve a given problem.

“Based on our findings, the majority of companies are still trying to manage complex applications with a combination of siloed tools, ‘all hands on deck’ interactive marathons, and tribal knowledge,” said Julie Craig, Research Director, Application Management at EMA. “The ability to automatically discover and manage the business transaction topology as the application itself changes is a significant challenge encountered by virtually every IT organization.”

In addition to EMA’s finding that most companies have under-invested in application-specific management tools, the survey also found clear purchasing preferences regarding future APM purchases:

■ Almost 75 percent identified “flexible deployment options” (supporting SaaS, on-premises, and/or hybrid deployments) as either “critical or important” factors for purchasing an APM solution.

■ More than 70 percent identified the “ability to monitor infrastructure as a service (IaaS) public cloud” as either critical or important.

■ When asked about their top “must have” features for an APM product purchase, respondents selected the following:

#1 feature preference: An integrated monitoring platform consolidating application and infrastructure monitoring in one solution

#2 feature preference: Cloud-readiness features necessary to monitor/manage application components hosted in public cloud

#3 feature preference: Support for trending and reporting

The EMA study shows that very few IT organizations have an accurate, comprehensive view of today’s complex application environment, business transactions and their dependencies. Unified Monitoring is a new way to manage applications proactively, by tracing and monitoring transactions from the end user through the entire application and infrastructure environment to help quickly and proactively solve performance issues and ensure excellent user experience. Companies no longer need to waste valuable time and resources on a dozen different tools that will likely just collect dust on the shelf.

EMA Survey Methodology: AppDynamics commissioned EMA to conduct a survey in May 2015 of nearly 300 IT professionals from small, midsized and large companies across both North America and Europe. For the purposes of the study, respondents were filtered to include only those actively involved in enterprise application development/management/delivery at the executive, middle manager, or "hands on" line staff levels.

Kalyan Ramanathan is VP Marketing at AppDynamics.

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

Franken-Monitoring - A Case of Too Many Tools

Most Organizations Have 11 or more tools to Manage Application Performance
Kalyan Ramanathan

In a recent interview, an IT operations director told us, “We frankly have too many tools, and many of them weren’t performing to our expectations.”

If you are an enterprise ops leader managing complex applications, you can probably relate to that statement. At AppDynamics, we call this “Franken-monitoring,” a situation characterized by many, usually too many, siloed tools — for application, server, database, end-user client, etc. — that provide varying levels of disparate visibility into IT applications.

The challenges with this approach include:

■ Tools have minimal integration or common context, which makes it near impossible to manage the application or its business transactions.

■ Tools are designed for subject-matter experts, so it’s hard to provide value to the ops team as a whole.

■ Tools have high total cost of ownership, since every tool has to be independently procured, installed and managed, and staff have to be trained in their use.

2015 APM Tools Survey Finds That Tools Are Underutilized and Solving Performance Problems is Still a Massive Challenge

We commissioned analyst firm Enterprise Management Associates (EMA) to get to the bottom of this. In the 2015 APM Tools Survey, EMA found that a majority of surveyed enterprises have 11 or more commercial tools in their arsenal to manage application performance.

Nearly two-thirds of respondents report that it takes at least three hours to determine the root cause of performance issues; one-third report that it takes six or more hours to find the source of an issue.

EMA’s survey indicated that the lack of application-focused solutions appears to contribute to current IT challenges, with IT teams often trying to manage modern, complex applications with siloed tools and primarily manual processes. Just about every user of monitoring tools complains about the challenges of having too many tools without any situational awareness. Current approaches to integrate these tools with solutions like MoM (manager of managers) or CMDB (configuration management database) have for the most part failed, because it is hard to stitch together these disparate solutions from different vendors.

Gartner recently did a survey that pointed exactly to this challenge. The key reasons (besides price) for poor APM adoption were, indeed, the complexity of the tools and poor integration between tools.

Specifically, the EMA study found:

■ Siloed and shelved monitoring tools: 65 percent of the companies surveyed indicated that they own more than 10 different commercial monitoring products. Nearly half also indicated that 50 percent or fewer of their purchased tools are actively being used.

■ Manual resources expended on application support: According to respondents, calls from users are the second-most frequent way IT organizations find out about application-related problems (27 percent cited detection by monitoring centers; 25 percent cited user calls). Line staff, those closest to the problem, report a significantly higher incidence, citing user calls as their first “heads up” 35 percent of the time.

■ Extensive people-hours required to solve a single application problem: IT organizations surveyed indicated that, for those application-related problems escalated beyond Level 1 support, mean time to repair (MTTR) is most often between five and seven hours; in addition, between three and four people are typically required to solve a given problem.

“Based on our findings, the majority of companies are still trying to manage complex applications with a combination of siloed tools, ‘all hands on deck’ interactive marathons, and tribal knowledge,” said Julie Craig, Research Director, Application Management at EMA. “The ability to automatically discover and manage the business transaction topology as the application itself changes is a significant challenge encountered by virtually every IT organization.”

In addition to EMA’s finding that most companies have under-invested in application-specific management tools, the survey also found clear purchasing preferences regarding future APM purchases:

■ Almost 75 percent identified “flexible deployment options” (supporting SaaS, on-premises, and/or hybrid deployments) as either “critical or important” factors for purchasing an APM solution.

■ More than 70 percent identified the “ability to monitor infrastructure as a service (IaaS) public cloud” as either critical or important.

■ When asked about their top “must have” features for an APM product purchase, respondents selected the following:

#1 feature preference: An integrated monitoring platform consolidating application and infrastructure monitoring in one solution

#2 feature preference: Cloud-readiness features necessary to monitor/manage application components hosted in public cloud

#3 feature preference: Support for trending and reporting

The EMA study shows that very few IT organizations have an accurate, comprehensive view of today’s complex application environment, business transactions and their dependencies. Unified Monitoring is a new way to manage applications proactively, by tracing and monitoring transactions from the end user through the entire application and infrastructure environment to help quickly and proactively solve performance issues and ensure excellent user experience. Companies no longer need to waste valuable time and resources on a dozen different tools that will likely just collect dust on the shelf.

EMA Survey Methodology: AppDynamics commissioned EMA to conduct a survey in May 2015 of nearly 300 IT professionals from small, midsized and large companies across both North America and Europe. For the purposes of the study, respondents were filtered to include only those actively involved in enterprise application development/management/delivery at the executive, middle manager, or "hands on" line staff levels.

Kalyan Ramanathan is VP Marketing at AppDynamics.

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