The SAM 5.2 beta is already underway, but it's not too late to get in on the action. And If you've been biding your time waiting for Beta 2, you're in luck! As of today, beta 2 of Server & Application Monitor 5.2 is now available to all existing APM/SAM customers under active maintenance. All you need to do to get your hands on the beta is sign-up. It's just that simple.

 

Native support for Microsoft's Hyper-V and a radically revamped template editor may be the star attractions, but the list of new features in this release hardly ends there! Let's take a look at two more impressive new features included in SAM 5.2 beta 2.

 

New Charts


SAM 5.2 New Charts.png

The recent release of NPM 10.3 included some cool new charts. While not enabled by default, these new charts can be added to any view to replace the older legacy charts you already know and love.

 

In SAM 5.2 beta 2, we similarly refreshed many of the out-of-the-box charts by incorporating the same charting library included in NPM 10.3. However, the SAM team put their own twist on an already cool feature by integrating the warning and critical thresholds into these new charts so you can quickly visualize how your collected statistics relate to these thresholds over time. These thresholds are represented on charts as red hued bands for critical, and yellow for warning, as seen in the image on the right.

 

Also new in beta 2 is the addition of a trend line on these charts. The trend line allows you to look at a large volume of statistical data and easily make capacity planning decisions based on this information. This functionality has existed in NPM for quite some time and now makes its way to SAM via these new chart resources.

 

Windows Event Log Monitor

 

The Windows Event Log Monitor first appeared in APM 3.1, and sysadmins everywhere have been relying upon it ever since. From the alerting of application problems to important security events, the Windows Event Log Monitor has been an intrinsic component of APM and SAM.

 

One item that's been missing from this component monitor, since its inception, has been the ability for users to know precisely which event triggered an alert. Because this component monitor type can be configured nonspecifically and alert on something as basic as any error in the application event log, it's important for IT support staff to know exactly what event was found before responding.

EventLog Message Details.pngThe SAM team sought to improve the Windows Event Log Monitor in version 5.2 by including an Event Log Message Details resource that displays all current and historic matching events for the configured component. This provides administrators with a detailed accounting of how frequently this condition is occurring, as well as when the last time a similar event occurred.  When you click on any event listed in the Event Log Message Details resource, a new window displays the full details of the corresponding event. This information can also be included as part of the email alert message using the new ${WindowsEventMessages} macro.

 

EventLog Message Details Opened.png

There's many more great new features in this release, so I encourage all existing SAM customers under active maintenance to signup and check them out for yourself! As always, we welcome your feedback. Feel free to respond to this post if you have any questions or comments regarding the beta. All existing beta participants are asked to post their feedback in the SAM beta forum.