In Part One of APMdigest's exclusive interview, Bojan Simic, President and Principal Analyst at TRAC Research, talks about the firm's new APM Spectrum report.
APM: What was your goal for the APM Spectrum?
TRAC: We had three key goals for the report: to dive deeper into the APM market, reduce some of the confusion around APM and make the information relevant and actionable.
We are publishing in an interactive format because there is so much information. If we put it in a PDF or Word document it would be close to 90 pages. So we have divided the report into bite-size chunks, based on your job role, your use case, the challenges that you are trying to address. You can quickly and easily see exactly what you care about.
APM: What exactly does the APM Spectrum cover?
TRAC: The report covers 30 angles in which to look at the APM market, which includes topics such as the nine submarkets of APM technologies that we identified; five key application performance challenges; the business areas that are being impacted by application performance issues; return on investment of APM solutions; the APM deployment process; vertical industries including telecom, healthcare, finance and retail; use cases including cloud, virtualization, mobility, Web services/Web APIs and Big Data; best practices; and recommendations.
In this APM Spectrum report we are not delving into which vendor is providing more capabilities — it is more about where they fit into different user requirements. True vendor evaluation is being conducted in our Hub studies and Vendor Index reports.
APM: Do readers of the report check off their particular needs and then get a unique recommendation?
TRAC: There are general recommendations that are relevant for all APM users, and then they get recommendations specific to their job role as either IT operations, business user, developer or CIO.
APM: Is the report mostly for organizations buying their first APM solutions, or could it be used for ongoing APM initiatives?
TRAC: It is really for both. If you look at the recommendations, some of them are how to get started with APM and how you create your APM strategy, but a lot of recommendations are also about how to make your current initiative more effective. It is not only from a technology perspective, we talk about organizational aspects as well.
APM: What is the biggest challenge a user faces when selecting an APM tool?
TRAC: That is a great question, and that is why TRAC built this APM Spectrum. There is a lot of confusion in the market. There are a lot of vendors in the market that have a very similar message. They talk about the same things, while sometimes doing completely different things.
One thing that the vendors did to themselves, they jump on some of the hot topics around APM, raise awareness about who they are, and they confuse the heck out of the market. All of a sudden they all look the same. We get a lot of requests from end-users to explain what exactly specific vendors do around APM.
We are trying to reduce all the confusion in the market, and show that APM is not one single market — it is a concept around managing the delivery of applications to end-users. There are at least nine submarkets of APM, and each has its own unique buying requirements. So we are showing people that one size does not fit all in APM. For the majority of end-users, there is no such thing as an APM solution that will take care of all of your needs.
Also, if you look at different use cases, these solutions are not as effective in every use case — cloud, Big Data, mobility. Even though you have a good APM product, you might find that your solution is not as effective when your environment starts changing and you start managing different use cases. So it is really more about finding the right mix of APM capabilities.
It is not about which approach to APM is better, but it is about who you are as an end-user and what you are using APM for.
APM: Did you find that most organization currently use a single APM solution or multiple tools?
TRAC: Our survey data shows that 71% of respondents are using more than one APM tool. And we did not survey only Fortune 500 and huge companies that are using everything under the sun for APM. Close to 50% of our survey respondents were actually SMB companies.
APM: According to the APM Spectrum, time to value is the key selection criteria for evaluating APM vendors. What is good vs. unacceptable time to value that most APM users would experience?
TRAC: I think that is one of the key stories of the study because it shows how the APM market has changed over the last couple years. APM products used take 3-4 months to deploy, with a couple of people working on it full-time, and a lot of consulting hours. For that reason, APM was not very appealing to many organizations. But, there has been a major shift in the market where deployment went from four months to a day or two. We are now seeing a day or two, sometimes a week, from the point you start deploying the solution to where you start seeing the value in the data coming back. But two or three months, even one month, is definitely too long.
Read Q&A Part Two: TRAC Research Talks About the APM Spectrum
