DevOps is changing the M in APM: Performance requires Management – not Monitoring


News: DevOps is changing the M in APM: Performance requires Management – not Monitoring

  1. Management Requires Collaboration; Monitoring Does Not.

    Application Performance Management involves a level of work and commitment that requires development, testing, and operations teams to work together. This is the minimum level of collaboration needed to accomplish the successful launch of an application.  Anything less falls under the alternate “M? – Monitoring.

    Monitoring fails because it only serves the Operations group and the other two play damage control by reacting to alerts. Most vendors take an approach that assumes collaboration is the sharing of a screen print, a report, or a log file.  This offers no detail of the problem(s) other than the limited information contained in an aggregated view.  Imagine someone looking at a picture of the Eiffel tower and claiming they have been there because they’ve “seen? it.  Would you collaborate with this person in planning your dream vacation to Paris?

    In order to have good collaboration you have to have a platform that everyone can agree on and adhere to.  The same is true for application performance.  Having the same rich data at all levels enables everyone to work together on solving the problem, without questions about the data or needless and time-consuming requests for more information.

    Continue reading the rest of the blog ...

  2. Some would argue that what you have presented is not in fact "management" but instead "meetings" and lots of them.

    My definition of management centers more around control that colloboration...control that is implemented directly within the software itself and without as little as possible human intervention. Control that can implement quality of service policies ( Control that increase the resilience of systems through adaptive controlled execution ( Control that allows the software to dynamically alter its own execution behavior based on past contextual execution behaviors (

  3. Hi William

    Good to see that you are still around - and to no surprise are you linking to your product pages :-)

    If all software problems (performance and functional) could "manage themself away" I guess we wouldn't continue writing about how to better manage these situations.

    All the best with your approach. Andi

  4. give me some credit[ Go to top ]

    hey I did link to pages under "research" which admittedly link to articles that our technology/product specific

    you can't deny that it is a much bigger and far better vision of "management" than having more meetings and tweets (cough) colloboration

    anyway self adaptive software is currently the area of research that offers the most promise in addressing complexity in managing systems

    technically this is the right direction whether it get acceptance in a mass market that has still SQL performance problems is an entirely different matter though I have some ideas to address this via a new "autoletic" entity

    well at least I am trying to doing something different and hopefully better, rather than copy the same yesterday approach that continues to not adequately address past, present and future problems ;-)