Tag Archives: 2012
.NET APM in SCOM 2012 Beta seems to have many of the features of the previous AVIcode version (5.7), but some of them are hidden. In this video, I am going to demonstrate that we can still collect callstack information, though it requires a bit more efforts to configure APM that way. Continue reading
AVIcode Configuration Assistant is not a service(though we can offer a service, too), neither it is a miraculous application that can configure AVIcode without human intervention (nothing can beat our consultants in that). Continue reading
There are a few things that bother me in the 2012 version of .NET Monitoring:
- No support for anything but web applications
- Very limited set of server-side configuration options that makes the product hardly usable for application deep-dive troubleshooting
- Separation of the product from the development teams. This one can be overcome to some extent by educating developers on the SCOM 2012 interfaces, but, still, it’s there.
t is sometimes difficult to ignore the desire to start monitoring just everything. It’s the easiest approach, and it can be implemented quickly. Just add “all namespaces”, add some of the system namespaces on top of that, and you’ll get enough details to satisfy any development team. The problem is that you’ll probably render your application unusable by doing that since users will have to spend minutes for what they could do in a just few seconds before that. Continue reading
From a certain standpoint, AVIcode brings Devops practices. There is no way to implement AVIcode successfully if operations team is isolated from the development team. And, if you look at it from a different perspective, AVIcode is much easier to implement in those organizations where Devops approach has been adopted already.