Category Archives: .NET Monitoring
It seems to be a common sales pitch for many .NET APM tool development companies to say that “our tool is not a profiler”. With 10 years of APM background I perfectly understand why it’s happening. You don’t want to … Continue reading
What is inlining? Pretty much, that’s the ability of a compiler to replace particular method calls with a functionally equivalent block of code where the method call is already removed. For example, any call to the following method could easily … Continue reading
After upgrading a System Center Operations Manager 2007 R2 management group that was integrated with AVIcode 5.7 to System Center 2012 – Operations Manager, when trying to edit new or existing AVIcode 5.7 templates in the Operations Console, one of these errors occurs.. Continue reading
Where we quite often assume that pro-active application monitoring is what’s really needed, it does not mean that re-active monitoring does not happen. Actually, it does happen, and, moreover, it’s probably how monitoring happens most of the times. Continue reading
System Center UI/functionality is not that familiar to the developers to feel comfortable with those tools. Development folks are used to the Visual Studio and other dev tools. At the same time, if there are people interested in APM data from the troubleshooting perspective, those are likely developers.
So, what if we wanted to bring APM data right to their world? Continue reading
.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
AVIcode is a relatively simple product when it comes to the installation. Being installed in the default configuration, it can identify performance/exception violations in the.NET applications that even developers might not be aware about. However, to identify an issue and to provide enough details about it are two completely different stories. Continue reading