Last week a performance engineer called Ben Bramley published a blog entitled “APM Market Disruptors – AppDynamics and New Relic“. The purpose of his article was to provide an overview of AppDynamics and New Relic, whilst also summarizing the key approaches each vendor/solution has taken to simplify and disrupt the APM marketplace.

Firstly, we’re thrilled to be recognized by a blogger, who in this case, had previous hands on experience with Application Performance Management (APM) products like OpTier, CA Wily, HP and dynaTrace. Secondly, whilst it was obviously good (and slightly nerving at times) to read our features and capabilities compared with another vendor (and the APM market in general), it was actually nice to see our freemium and SaaS based go-to-market strategy being recognized as well. I guess these things were actually the main reason why a blogger could access, compare and contrast two next generation APM solutions in the first place. It’s not like IBM, CA or Compuware would make their APM solution available to the masses for evaluation, let alone welcome an independent opinion.

You can read Ben’s blog article in full here.

App Man.

Update: HP does in fact offer their solution (HP Diagnostics v9) via trial, but you’ve got to download and install 4GB of their software.  In the time it takes to do this you could already be up and running with AppDynamics Lite.

APM Market Disruptors, AppDynamics vs New Relic, application monitoring, Application Performance Management, CA Wily, Dynatrace, HP, IBM, New Relic, OpTier, Web Monitoring

I have yet to meet anyone in Dev or Ops who likes alerts. I’ve also yet to meet anyone who was fast enough to acknowledge an alert, so they could prevent an application from slowing down or crashing. In the real world alerts just don’t work, nobody has the time or patience anymore, alerts are truly evil and no-one trusts them. The most efficient alert today is an angry end user phone call, because Dev and Ops physically hear and feel the pain of someone suffering

Why? There is little or no intelligence in how a monitoring solution determines what is normal or abnormal for application performance. Today, monitoring solutions are only as good as the users that configure them, which is bad news because humans make mistakes, configuration takes time, and time is something many of us have little of.

Its therefore no surprise to learn that behavioral learning and analytics are becoming key requirements for modern application performance monitoring (APM) solutions. In fact, Will Capelli from Gartner recently published a report on IT Operational Analytics and pattern based strategies in the data center. The report covered the role of Complex Event Processing (CEP), behavior learning engines (BLEs) and analytics as a means for monitoring solutions to deliver better intelligence and quality information to Dev and Ops. Rather than just collect, store and report data, monitoring solutions must now learn and make sense of the data they collect, thus enabling them to become smarter and deliver better intelligence back to their users.

Change is constant for applications and infrastructure thanks to agile cycles, therefore monitoring solutions must also change so they can adapt and stay relevant. For example, if the performance of a business transaction in an application is 2.5 secs one week, and that drops to 200ms the week after because of a development fix. 200ms should become the new performance baseline for that same transaction, otherwise the monitoring solution won’t learn or alert of any performance regression. If the end user experience of a business transaction goes from 2.5 secs to 200ms, then end user expectations change instantly, and users become used to an instant response. Monitoring solutions have to keep up with user expectations, otherwise IT will become blind to the one thing that impacts customer loyalty and experience the most.

Read the Full Post…

Analytics, apm, Application Diagnostics, application monitoring, Application Performance Management, Behavioral Learning, Business Transaction Management, Business Transactions, CEP, Complex Event Processing

AppDynamics has experienced significant growth over the past three years, here’s a quick summary of our key highlights.

Embed this image on your site:
<a href="http://www.appdynamics.com/blog/2012/01/20/appdynamics-growth/" title="AppDynamics Growth - Not Bad for 3 Years"><br /> <img src="http://www.appdynamics.com/blog/wp-content/uploads/2012/01/AppDynamics_growth_infographic2.png" alt="AppDynamics Growth in 2011" /></a><br /> <br/>Source: <a href="http://www.appdynamics.com" title="AppDynamics Application Performance Management Tools">AppDynamics: Application Monitoring Company</a><br/>

apm, APm SaaS, APMaaS, appdynamics, AppDynamics Growth, application monitoring, Application Performance Management, Business Transaction Management

When I joined AppDynamics less than a year ago, we were situated in a 6,000 sq ft “cozy” office on 2nd and Brannan. On my first day I was greeted with a MacBook Pro and was asked to find a spare desk amongst the boxes and carnage of a typical startup environment. To my left was a relentless engineering and UI team, and to my right was a fired up sales and marketing team, and a quietly confident Founder and CEO, Jyoti Bansal who made all of this happen. Across the office was a shiny gold bell mounted on the wall, which rang every time AppDynamics closed a new customer. In the last year I can honestly say that shiny bell hasn’t stopped ringing, and is the biggest adrenaline boost one can get while working.

Read the Full Post…

apm, appdynamics, AppDynamics Funding, appdynamics lite, application monitoring, Application Performance Management, CA Wily, Compuware Dynatrace, Dynatrace, HP BAC, HP Diagnostics, IBM, Kleiner Perkins, New Relic

2011 was an amazing year for AppDynamics. We experienced tremendous growth and success, largely down to the many customers around the world who believed in our vision, technology, and ability to help Dev and Ops teams better manage application performance in production. The Application Performance Management (APM) market isn’t an easy market to succeed in, with well over 30 vendors competing against each other. In just three years we’ve managed to take on the big players like Compuware DynaTrace, CA Wily, HP and IBM to change the industry perception that APM is expensive to own and difficult to deploy/use.

We feel APM should be for everyone. It should be affordable, it should be easy to deploy, and easy to use. APM should not be a luxury that only an elite group of enterprises can afford. Today, we have customers who monitor applications with 5 nodes, 50 nodes, 500 nodes and 5,000 nodes. Application performance impacts organizations of all sizes; that’s why we wanted our APM solution to be accessible to the masses over the web via our free download and SaaS trial. We wanted to be transparent with our buyers and demonstrate that they can evaluate and use our solution all by themselves with no account manager or technical consultant by their side. We really wanted prospects to see for themselves that APM can be simple to deploy and easy to use.

A major validation of this market disruption was when a customer called Karavel in France was looking for an APM solution and evaluated CA Wily, Compuware dynaTrace and AppDynamics. Karavel requested a trial, downloaded our software and we sent them a trial license key for 30 days. The whole AppDynamics install, deployment and evaluation was solely conducted by the customer on their own. This might not sound that impressive, but this is what the software buying experience should be all about: the customer and the solution. If the customer can’t install, deploy and evaluate an APM solution on their own, how will they manage this process when it comes to a production deployment? Software should sell itself these days–if it requires an army of people to sell it, it probably requires an army of people to implement it as well.

You can read the full Karavel press release here:
http://www.appdynamics.com/press/press-release-01-03-12.php

Full case study is available here also:
http://www.appdynamics.com/documents/case_studies/AppDynamics_CS_Karavel.pdf

Remember, software like APM doesn’t have to be complex and expensive. With the internet these days, there is no excuse why a prospect can’t download or evaluate solutions online in just a few hours.

App Man.

apm, appdynamics, application monitoring, Application Performance Management, CA Wily, Compuware, Dynatrace, HP BAC, IBM ITCAM, New Relic, OpNet, OpTier, Quest Foglight

One of my colleagues this week was consolidating the results from our recent Application Performance Management survey, and one interesting finding was that 40% of customers have at least one release cycle a month. Out of those respondents, one third experience a Severity-1 incident each month as well. That’s a pretty compelling pair of statistics, and they might explain the continued frustration and conflict between development and operations teams. It’s also perhaps the reason why this DevOps underground movement can no longer be ignored (even by Gartner). There is no doubt development organizations have become agile, but does deploying this frequent change make the business more or less agile? For example, if one in three releases creates a Severity-1 incident, then surely agile development becomes a risk to the business. We’re at the point where Operations either has to start managing change better or simply restrict the amount of change that can occur.

So why are Sev 1 incidents so common? Based on my experiences and customer interaction, I’d strongly argue that testing in development isn’t enough. At the very least, it’s certainly not an insurance policy for deploying an application in production. When a Formula 1 team designs a car in a wind tunnel and tests it on a simulator pre-season, they don’t assume that the performance they see in test will mirror the results they see in a race. Yet, that is pretty much what happens today in the application development lifecycle. Development teams build and test their apps in pre-production before handing it off to operations for deployment in production, and they assume everything will work just fine. This is probably the worst assumption IT has made over the last decade, because development and production environments differ significantly. It’s also a lame excuse for any development team to use when a production issue occurs: “Well it ran fine in test so you must have deployed it wrong.” Yes people make mistakes occasionally, but if one in every three releases has an issue, deployment error may not be the sole reason. If development never get to see how their baby runs in production, they’ll never learn how to build robust, scalable, and high-performance applications.

Read the Full Post…

apm, appdynamics, appdynamics lite, application monitoring, CloudTest, HP LoadRunner, Load Runner, Load Testing, Production Monitoring, Production Testing, SOASTA

apm, application monitoring, Application Performance Management, Baselining, BTM, Business Transactions, CA Wily, Lew Cirne, normal performance, Wily Introscope

On Wednesday I delivered a keynote at WJAX in Munich. Everything went really well, but I was a little shocked at the response I got when I asked the audience “How many of you monitor the performance of your apps in production?” As I scanned the audience, I counted 9 out of ~950 developers had put their hands up, meaning about 1% had visibility of how their applications actually performed in production. I know what you’re thinking: “But isn’t application performance in production the responsibility of Operations?”  Well, it is and it isn’t. Most organizations think that when an application has an issue, it’s related to the infrastructure it runs on. That’s like saying when a car crashes, it’s because a part failed on the car whereas in actual fact most accidents are caused by the driver. Yes, hardware fails occasionally, but application logic and configuration drives how infrastructure resource is used, which is why most issues today occur when new code is deployed in production.

Read the Full Post…

apm, appdynamics, appdynamics lite, AppDynamics Pro, application monitoring, Application Performance Management, MTTR, Performance Bottlenecks, Production Monitoring, Slow Application, WJAX

The majority of us in IT are specialists, with the exception of a few VPs of engineering who are “special” in their own “special” world of being “special.” What I mean by this is that no single person has the skills or experience to do everything well in IT. IT is too big for me to explain or summarize in a few words, other than it requires a lot of different people with different skills to make it tick along. Despite applications being the living breathing entities of the business, a large portion of folk in IT have little context of how applications are built, how they execute, and how they consume resource across the IT infrastructure. Many people simply don’t care as their responsibilities are completely void of anything application related. That’s fine–but the reality is that everyone in IT should have one eye on the business. The whole reason IT exists is so the business can be more competitive and make more money. If this happens, IT gets more budget and is allowed to innovate more. IT and the business need each other to survive, which is why when applications slow down or break, both parties bitch at each other.

Operations need better visibility

Unfortunately for both the business and IT, the people (Operations) who manage the performance and availability of applications in production aren’t application experts. They are also not stupid either; their skills sets are wide and broad across many technologies and platforms that underpin applications. They manage a lot of things that application developers take for granted, like networks, databases, storage and virtualization. While Operations monitor the health of these infrastructure components, they often get bombarded with crap from the business when end users and business transactions are being impacted by slow performance, despite all system monitoring showing everything is fine. This lack of understanding between the Business and Operations is because both parties see things from different perspectives.

Read the Full Post…

apm, appdynamics, application monitoring, Application Performance Management, BTM, Business Transactions, CA Wily, Compuware, DevOps, Dynatrace, HP BAC, IBM Tivoli, Nastel, OpNet, OpTier

What happens when mission critical Java applications slow down or keep crashing in production? The vast majority of IT Operations (Ops) today bury their heads in log files. Why? because thats what they’ve been doing since IBM invented the mainframe. Diving into the weeds feels good, everyone feels productive looking at log entries, hoping that one will eventually explain the unexplainable. IT Ops may also look at system and network metrics which tell them how server resource and network bandwidth is being consumed. Again, looking at lots of metrics feels good but what is causing those server and network metrics to change in the first place? Answer: the application.

IT Ops monitor the infrastructure that applications run on, but they lack visibility of how applications actually work and utilize the infrastructure. To get this visibility, Ops must monitor the application run-time. A quick way to get started is to use the free tools that come with the application run-time. In the case of Java applications, both JConsole and VisualVM ship with the standard SDK and have proved popular choices for monitoring Java applications. When we built AppDynamics Lite we felt their was a void of free application monitoring solutions for IT Ops, the market had plenty of tools aimed at developers but many were just too verbose and intrusive for IT Ops to use in production. If we take a look at how JConsole, VisualVM and AppDynamics Lite compare, we’ll see just how different free application monitoring solutions can be.

Read the Full Post…

apm, appdynamics lite, application monitoring, Application Performance Management, Free application monitoring, Java Monitoring, JConsole, JVM, JVM Monitoring, Oracle, Oracle Java Monitoring, VisualVM