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

The Next Level of Server Monitoring - SAM 5.5 Beta 3

Product Manager

If you're running Server & Application Monitor (SAM) or Network Performance Monitor (NPM) then chances are you're already monitoring many of your servers critical components, such as CPU, Memory, and Virtual Memory utilization, as well as volume usage. If you're running SAM 5.x then you're probably monitoring your servers hardware health, too. These are all vitally important components that should be monitored, since they all contribute to the performance and availability of the servers, and the applications hosted on them.

In SAM 5.5 Beta 3 (now available) we've taken server monitoring to the next level. First, by expanding upon our server hardware health monitoring introduced in SAM 5.0, which included support for Dell PowerEdge, HP Proliant, IBM X-Series, and VMware ESX/i hosts. In this beta, you'll find added support for server blade chassis such as Dell's M1000e, HP's C7000 and C3000; because monitoring the chassis your servers are in is just as important as monitoring the servers themselves.

Dell M1000e.pngHP C7000.png

Next, we turned our attention to storage. Up to now SAM has had very limited visibility into storage beyond basic volume usage. To make matters worse, a paradigm shift spearheaded by Microsoft has changed how we look at and think about storage on Windows systems today. No longer are we bound by the limits of 26 letters of the alphabet when creating new volumes on our Windows systems. Windows Volume Mount Points make it possible to add storage wherever we need it. However, up until now it's been very difficult to monitor these Mount Points like traditional volumes.

Windows Volume Mount Point.png

So in SAM 5.5 beta 3 we added native support for Windows Volume Mount Points, and made monitoring them as simple as monitoring any other volume in Orion.

Mount Point List Resources.pngMount Points.png


But we didn't stop there. Today storage is the leading cause of server and application performance issues. Having visibility into storage volume performance, such as I/Os per-second, queued disk I/O, and latency, from within the SAM web console alongside other key performance indicators allows you to isolate where performance bottle necks are occurring on your server, and which applications are effected. So in SAM 5.5 Beta 3 that's exactly what we did.

  Disk Queue Length.png  Avg. Disk sec Transfer.png

Best of all, these new volume performance metrics simply appear on your Volume Details view. No configuration necessary for volumes already monitored via WMI. These new resources will also automatically appear for any new volumes, including Windows Volume Mount Points you chose to monitor after upgrading. Again, no configuration necessary beyond selecting the volume to be monitored.

Total Disk iOPS.png

If you're currently running SAM, and are under active maintenance, we welcome you to sign-up here and download the SAM 5.5 beta today. We'd love your feedback on the features we've implemented so far. For more information on some of the other features included in the SAM 5.5 beta, including the Windows Service Control Manager, please checkout my earlier blog post

15 Comments
Level 9

AlterEgo

These are very nice.

Can we ensure that this next NPM verison release will improve scalability???

I'm already at 12 Servers and a DB. Due to security restrictions, the system must in a Data Center.

Current architecture is now at limit, devices cannot have 12 separate IPs. If this version will allow for clustering of pollers, and and prenting a single IP to the Network for responses we can take our ACLs from 12 IPs to 4 is 3 server clusters is in fact an architecture supported in this next version.

This is what I've been told, and we have funding to redesign our NPM configuration. Just trying to get some confirmation. I don't have a test bed so I'm not going to put the beta on our production until full release. Just trying to get all parties on the same page within our organizations to get the full release ready with the appropriate infrastructure.

Thanks

Radioman


Product Manager
Product Manager

, I appreciate your concerns but this blog posting is regarding Server & Application Monitor (SAM), not Network Performance Monitor (NPM). This question may be better suited for the forum.

Level 9

SAM Response.bmp

Product Manager
Product Manager

Correct, there is a reference to NPM within my blog post. This is because NPM provides some very basic server monitoring capabilities.SAM however expands far beyond NPM's base server monitoring to include visibility into the applications running on those servers, the underlying server hardware health, and much more.

Level 20

This is huge move in the right direction... can't wait till this goes release... we need our blade centers monitored and we have TONS of windows servers with mount points that need to be monitored.  :^}  Glad to see you're on top of this aLTeReGo

Level 13

Excellent added features! The community has been eagerly awaiting for native Mount Point monitoring. Soon I'll be able to retire my SQL Disk Monitoring templates! Also the focus on storage is great. Having actual IOPS and storage performance numbers mean that Sysadmins and Storage Admins can speak the same language. Kudos!

Level 10

Whats under the Chassis expanded list for HP C7000? You expanded all but the Chassis option. Are you showing blade information?

Product Manager
Product Manager

The blades themselves are monitored independently of the chassis, but the Chassis category does roll up the status of any blades in the chassis that might have issues.

Level 17

We just installed SAM 5.5 RC1 into our dev environment (which also has NPM 10.4.1). How do you add Volume mount points to an existing (ICMP/SNMP) node? Do you have to convert it to poll using ICMP/WMI?

Thanks!

Product Manager
Product Manager

Volume Mount Point Monitoring is only available for WMI managed nodes. Microsoft does not make this information available via SNMP.

Level 11

can IOPS and disk queue length be used via SNMP?

Product Manager
Product Manager

No. Unfortunately Microsoft does not expose this information via SNMP.

Level 9

I really need this as I'm using a SAM custom poller and it is a PITA.  Every time I add a new mount point I have to go set it up in the template.  It sucks. I monitor everything via SNMP.  I just did a test on a node using WMI and I see that it only sees CPU and volumes.  What about NICs, L2 and L3?  Please don't make this an either/or type choice.  I get really tired of "Here is our great new feature!"  To use it you need to stop using our previously great feature that you still depend on.  Something that appears too common in technology these days.

Product Manager
Product Manager

Windows Interface Monitoring and topology data (L2/L3) is also part of the SAM 5.5 Release, so you shouldn't need to make a choice between monitoring mount points or interfaces. You can have your cake and eat it too.

Level 13

can you add support for cisco ucs B C and E series servers

also Netapp NAS and EMC SAn storage arrays?