cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Announcing the Official Release of Server & Application Monitor 5.2

Product Manager

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

Component Settings.pngAfter 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.

SNMP Monitor.png

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 1.3.6.1.4.1.1230.2.7.2.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

12 Comments
Level 12

Should we upgrade SAM 5.2 RC2 to GA?

Product Manager
Product Manager

Yes. If you are running the SAM 5.2 RC1 or RC2 you should upgrade to the GA build that's available through your customer portal.

Level 14

What does Hot Fix 1 address?

Product Manager
Product Manager

From the ReadMe.txt included with the hotfix "fixes an issue where HTTP Monitor, HTTPS Monitor, Form Login Monitor, and Web Link Monitor may convert URLs to lowercase characters which can cause false Down statuses and HTTP 404 errors if the web server is case sensitive."

Level 13

Its a great release!  The template editing enhancements are very welcomed!  Great job guys!

Level 9

I Already apply the hot fix and still the HTTP monitor is not functioning? What can be checked?

Product Manager
Product Manager

The hotfix only addresses issues monitoring web servers that are case sensitive, such a Linux/Unix. If you look at the web server logs you will see the URL is all lower case where in the component monitor it has mixed case such as "http://some.server.com/MyApplication" becomes "http://some.server.com/myapplication". For web servers that enforce cases sensitivity the second URL would likely result in a 404 Page Not Found Error. If this is what you're seeing I recommend reapplying the hotfix following the instructions included in the archive.

If this is a separate issue entirely, or your still having case sensitive URL issues after properly applying the hotfix I recommend opening a case with support so we can look through your debug diagnostic logs and figure out what's going on. Before opening a case however, copy the URL as entered in the the component monitor and paste it into a web browser on the Orion server to ensure it's properly entered, and is reachable from the Orion server.

Level 9

I am testing the HTTP monitor by going into the Edit Application Monitor tool, and running the component test from there to ensure that I am allowing time for a response, and to get any details on what is happening. With the new DLL from the hot-fix, it gives the down with “unknown” error message. When I swap the DLL back in and restart the services, and then test using the exact same method, I get the 404 error message again.  Any suggestion?

Product Manager
Product Manager

Please ensure that once you've replaced the DLL you open the file properties and click "unblock" before starting the Orion services.

probes.dll.png

Level 9

In win2008R2 that is not appearing.

Product Manager
Product Manager

The screenshot above was take from a Windows 2008R2 server, so it may be a permissions issue. Try again logging in to the server using the local administrator account.

Level 9

I appreciate your help! The problem I was having was due to the DLL being untrusted. Due to a group policy in place for users that applied the “Do not preserve zone information in file attachments” setting I was unable to see the “Unblock” box on the hotfixed DLL. I found a user that did not have that policy applied and then was able to see the Unblock button and click it, which resolved my issue entirely after a services restart.