Today I'm pleased to announce the general availability of Server & Application Monitor 5.2. All current SAM & APM customers under active maintenance can download the upgrade immediately through their customer portal.
In the months leading up to this release, I've made several postings in the Product Blog that highlight many of the new features and enhancements included in SAM 5.2. Most notable amongst these new features is added support for Microsoft® Hyper-V. In fact, SAM 5.2 will be among the first products available to support Microsoft's latest Hyper-V v3.0 that's included as part of Windows 2012.
SAM 5.2 also includes many other great new improvements, such as a completely overhauled template editor featuring multi-edit, awesome new charts, hardware health & Real-Time Process Explorer improvements, as well as radical enhancements to the Windows Event Log Monitor. Today I'll touch on some of the equally as important, but lesser known features included as part of this release.
Component Details Resource
After upgrading to SAM 5.2 you will find a new Component Settings resource on any Component Details view. The information displayed in this resource is completely dynamic based on the type of monitor being viewed, and the specific application settings defined within the Component Monitor.
In earlier versions of APM and SAM the information contained in this resource was only available to admins who had the ability to edit application templates. This new resource allows all users of the system access to this vital troubleshooting information.
Now with this new Component Settings resource and the Expert Knowledge included with most of our out-of-the-box Application Templates; should your helpdesk staff notice the number of Lazy Writes per-second on your SQL Server is in a warning or critical state for instance, they'll know precisely what a Lazy Write is, which SQL instance is affected, and how to resolve the issue. They'll also see any User Notes that have been defined in the template by the IT staff that may contain additional troubleshooting or escalation steps.
Enhanced SNMP Monitor
Improvements have also been made to the SNMP Monitor in this release. Previous releases of APM and SAM only supported the basic SNMP GET method. SAM 5.2 now allows users to leverage the more flexible GET-Next method for creating more dynamic monitors. Unlike an SNMP GET, the GET-Next method retrieves the next value of the OID in the tree, which means that providing the instance value as part of the OID is not required. This is particularly useful when retrieving table data or variables that cannot be specifically named.
We've also added a Count Statistic as difference option, which functions similar to the Rate setting in the Universal Device Poller that's included with NPM. Using this new option allows you to monitor SNMP counters as if they were rates. For example, if you wanted to track the volume of malware detected by your Mcafee Web Gateway, you'd likely monitor the 184.108.40.206.4.1.1220.127.116.11.1.2 OID. However, the statistic returned from this OID is an ever increasing counter that only resets to zero when the device has been rebooted. What if you needed to track the number of viruses detected per-hour or day? Or what if you wanted to configure an outbreak alert to notify you if the number of viruses detected by the gateway suddenly spiked? This is where the Count Statistic as Difference setting becomes a very useful and powerful option in your monitoring arsenal.
So here I've given you two more great new reasons to upgrade to SAM 5.2 today. As always, if you have any questions regarding any of the new features in SAM 5.2, you can reference the Administrators Guide, our online Knowledge Base, or post your question to the SAM forum on Thwack. If your matter is more urgent, you can always open a support case, and one of our Support Engineers will be happy to assist.
Virtualization Monitoring With Server & Application Monitor 5.2