locked
Is AVICode more of a Dev monitoring tool? RRS feed

  • General discussion

  • Hello,

    How is everyone using their AVICode implimentation?  Are you using it more in your development environment or in production?  It seems to me AVICode servers the most value in a development enviroment when applications are getting built.  But, after all the bugs have been found and the application is moved over into production does AVICode still server the same purpose?

    Thanks,

    Tom


    Tom Martin Email: tmartin@caa.com
    Saturday, December 3, 2011 1:21 AM

All replies

  • Are you sure all your bugs are found while in dev/test/qa environment? All performance bottlenecks? Have you tested all of the random usage patterns that only real user can generate? What about modern applications in this DevOps world, when you deploy multiple times a week/day? What about that service acount which all of a sudden gets disabled by human error and you start getting "logon failures" somewhere in your app - maybe in some background processing - and the Operations team needs to react quickly?

    This is a bit of a philosophical question... but we believe AVicode is useful in production, and that is the reason why we have integrated it with Operations Manager 2012 - which is primarily a monitoring solution. We also think it is important to bridge the Developers and the Operations world so that the business is more efficient.

    HTH,

    Dan

    Saturday, December 3, 2011 2:59 AM
  • ... but we believe AVicode is useful in production, and that is the reason why we have integrated it with Operations Manager 2012 - which is primarily a monitoring solution ...

    I am evaluating OM12RC now but it seems that not so much of APM can be done for more complex deployments and OM12. Sure you can monitor a web app in IIS 7.0 but if you have other components working as windows services you're out of luck...  Will final OM12 include full AVICode like "deep dive" into all our .net apps deployed as windows services?

    Thanks!

    Kuba

    Wednesday, December 14, 2011 3:23 PM

  • This is a slightly different question again :-)

    Time and resource limitations kept us from supporting more than IIS7 in this release. There was a lot of work done in areas that can be overlooked: security, localization/globalization, ease of use, etc.
     
    We tried to make it easier to setup, simpler to configure, cheaper to maintain. Adam has written about some of the advantages of having a full monitoring solution that encompasses both applications and systems and shows here how easy it has become to configure http://blogs.technet.com/b/server-cloud/archive/2011/11/11/application-performance-monitoring-with-operations-manager-2012.aspx and Sergey here follows the same theme http://blogs.msdn.com/b/sergkanz/archive/2011/09/13/cut-the-monitoring-price-application-monitoring-investments.aspx

    We are working on extending what we can support after RTM. I can’t share any timelines right now as we’re still focused on shipping the current version.

    Wednesday, December 14, 2011 5:17 PM
  • Daniele is spot on as he normally is but for the purposes of future readers I want to add a few thoughts. Avicode or APM in SCOM is  a monitoring tool not a devlepment debugging and profiling tool. Developers have those and in theory have been sending apps to prodcution that have been tested and bugs repaired. The problems is not everything can be accounted for and problems will always arise, so when that happens how do you get alerted to that, then how do you know where and how bad it is. Then in some cases it is development related and not enviroment so how do you get the devs the details to work on it?


    Shawn Gibbs

    Thursday, February 9, 2012 2:35 PM
    Moderator