Franken-Monitoring - A Case of Too Many Tools
Most Organizations Have 11 or more tools to Manage Application Performance
August 06, 2015

Kalyan Ramanathan
AppDynamics

Share this

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.

Share this

The Latest

October 17, 2019

As the data generated by organizations grows, APM tools are now required to do a lot more than basic monitoring of metrics. Modern data is often raw and unstructured and requires more advanced methods of analysis. The tools must help dig deep into this data for both forensic analysis and predictive analysis. To extract more accurate and cheaper insights, modern APM tools use Big Data techniques to store, access, and analyze the multi-dimensional data ...

October 16, 2019

Modern enterprises are generating data at an unprecedented rate but aren't taking advantage of all the data available to them in order to drive real-time, actionable insights. According to a recent study commissioned by Actian, more than half of enterprises today are unable to efficiently manage nor effectively use data to drive decision-making ...

October 15, 2019

According to a study by Forrester Research, an enhanced UX design can increase the conversion rate by 400%. If UX has become the ultimate arbiter in determining the success or failure of a product or service, let us first understand what UX is all about ...

October 10, 2019

The requirements of an APM tool are now much more complex than they've ever been. Not only do they need to trace a user transaction across numerous microservices on the same system, but they also need to happen pretty fast ...

October 09, 2019

Performance monitoring is an old problem. As technology has advanced, we've had to evolve how we monitor applications. Initially, performance monitoring largely involved sending ICMP messages to start troubleshooting a down or slow application. Applications have gotten much more complex, so this is no longer enough. Now we need to know not just whether an application is broken, but why it broke. So APM has had to evolve over the years for us to get there. But how did this evolution take place, and what happens next? Let's find out ...

October 08, 2019

There are some IT organizations that are using DevOps methodology but are wary of getting bogged down in ITSM procedures. But without at least some ITSM controls in place, organizations lose their focus on systematic customer engagement, making it harder for them to scale ...

October 07, 2019
OK, I admit it. "Service modeling" is an awkward term, especially when you're trying to frame three rather controversial acronyms in the same overall place: CMDB, CMS and DDM. Nevertheless, that's exactly what we did in EMA's most recent research: <span style="font-style: italic;">Service Modeling in the Age of Cloud and Containers</span>. The goal was to establish a more holistic context for looking at the synergies and differences across all these areas ...
October 03, 2019

If you have deployed a Java application in production, you've probably encountered a situation where the application suddenly starts to take up a large amount of CPU. When this happens, application response becomes sluggish and users begin to complain about slow response. Often the solution to this problem is to restart the application and, lo and behold, the problem goes away — only to reappear a few days later. A key question then is: how to troubleshoot high CPU usage of a Java application? ...

October 02, 2019

Operations are no longer tethered tightly to a main office, as the headquarters-centric model has been retired in favor of a more decentralized enterprise structure. Rather than focus the business around a single location, enterprises are now comprised of a web of remote offices and individuals, where network connectivity has broken down the geographic barriers that in the past limited the availability of talent and resources. Key to the success of the decentralized enterprise model is a new generation of collaboration and communication tools ...

October 01, 2019

To better understand the AI maturity of businesses, Dotscience conducted a survey of 500 industry professionals. Research findings indicate that although enterprises are dedicating significant time and resources towards their AI deployments, many data science and ML teams don't have the adequate tools needed to properly collaborate on, build and deploy AI models efficiently ...