Skip navigation

Product Blog

April 2018 Previous month Next month

Starting with VMAN 8.0, and continuing with 8.1  we've streamlined how you deploy and use VMAN.  Virtualization Manager 8.2 , the latest edition of these efforts, is now available on your Customer Portal.

 

One of the biggest pain points that surfaced over the last 2 releases was that the process for adding virtualization nodes to be monitored was not intuitive. This is solved with a new simplified workflow!

 

Whether choosing to add a Node or setting up a Discovery job, we've updated those entry points to direct you to the new, separate workflow.

 

Add a Node - Select VMware vCenter or Hyper-V devices
Network Discovery - Add VMware vCenter or Hyper-V devices
All Settings -  Add VMware vCenter or Hyper-V devices

 

Once you click on any of those entry points you'll be able to get started monitoring your environment with a few simple clicks.

 

Add a Virtual Object for Monitoring
See the thresholds that apply to your virtualization manager entities
Click Finish and you're successfully on your way to monitoring your virtualization environment

 

If you identified any thresholds that you'd like to tweak, simply navigate to All Settings -> Virtualization Settings to update your thresholds. Within a few clicks, you're ready to take advantage of capacity planning, recommendations and much more!

 

Get Started with Documentation

VMAN 8.2 Release Notes

VMAN 8.2 Getting Started Guide

VMAN 8.2 Administrator Guide

VMAN 8.2 Deployment Sizing Guide

Applications talk to each other, and you should know who they are talking to

 

Applications constantly rely on communication between different servers to deliver data to end-users. The more applications end-users require to do their job, the greater the complexity of application environments and those communication based relationships.

With the release of Server & Application Monitor 6.6, we introduced an Orion Agent based feature, called Application Dependencies, which enables system administrators to quickly gain an understanding of which applications servers are talking to one another, as well as see related metrics, to help with troubleshooting application performance issues.

 

How do you enable it?

The ability to discover and map Application Dependencies is enabled by default. This allows SAM to actively collect inbound and outbound communication at the application process level. This is paired with an ability to collect connection related metrics (latency and packet loss), which is disabled by default. You can find all of the configuration options in the Application Connection Settings section of the Main Settings & Administration screen.

 

What does it show you?

At its core, Application Dependencies help you understand if application performance issues are associated with server resource utilization or network communication. For example, Microsoft Exchange is heavily dependent on Active Directory for authentication and other services. Application Dependencies show you the relationship, and the communication, by adding a few new resources in SAM.

 

The two main areas where you can see the Application Dependency information. One area is in a new widget that is available on application and node details pages. This widget will show you the discovered application dependencies, specific to that monitored application or node. Notice in the screen below that you can see where multiple Exchange servers have a dependency on the Active Directory server, ENG-AUS-SAM-62, and more specifically the Active Directory service that is running on it.

 

The second area where you can see Application Dependency information is in the connection details page, which is linked from the above mentioned connections widget. This will allow you to see all of the application monitors, and associated processes, process resources metrics, and ports, responsible for the discovered communication, between two specific nodes. You will also see the latency and packet loss data, if you have enabled the Connection Quality Polling component. The screen below shows the relationship between ENG-AUS-SAM-62 (Active Directory) and ENG-AUS-SAM63 (Exchange), in greater detail.

What’s going on under the covers?

There are two, new Orion Agent plug-ins that help deliver this new functionality. One is the Application Dependency Mapping plug-in, and the other is the Connection Quality Polling plug-in.

The Application Dependency Mapping plug-in is responsible for collecting the active connection data from the server. That information is then sent back to the Orion Server, where it is correlated with component monitor and node data, already being collected by SAM (Note: You must have at least one component monitor, like the process monitor, applied to the server). As SAM matches the collected data from the different application servers, it creates the connection details pages and populates the connection widget.

 

The Connection Quality Polling plug-in is responsible for a synthetic probe, which measures latency and packet loss. This accomplished by sending TCP packets to the destination server, on the specific port identified by the active connection information collected by the Application Dependency Mapping plug-in. It is important to note that the Connection Quality Polling plug-in includes the NPCAP driver for use with this synthetic probe.

 

If you would like to read more about how this feature works, you can find more information in the SAM administrator guide.

 

Is that it?

Application Dependencies is not the only feature that was released in SAM 6.6. You can read more about the other features in the release notes. You can also check out Application Dependencies, live in action, in the online demo.

I am happy to announce General Availability of Storage Resource Monitor 6.6.   This release continues the momentum of supporting FLASH and HYBRID arrays that were highly requested by you on THWACK!  We've also updated to SRM to the latest version of the Orion® Platform and installer, so you'll enjoy the benefits of easier upgrades and participation in all the latest Orion® features.  Check out the SRM 6.6 Release Notes for more information about installing, upgrading and new features and fixes.

 

New Array Support

Support includes all the standard features you love: capacity utilization and forecast, performance, end to end mapping in AppStack, and integrated performance troubleshooting in PerfStack.  We also were able to squeeze in Hardware Health for all these arrays too!

  • EMC Unity
  • HPE Nimble
  • INFINIDAT InfiniBox
  • IBM V9000

Now for some screenshots for your viewing pleasure!

 

Monitoring EMC Unity

SummaryBlock StorageFile StorageHardware Health
EMC Unity Monitoring SummaryEMC Unity Block Storage Monitoring EMC Unity File Storage Monitoring EMC Unity Hardware Health Monitoring

 

Monitoring HPE Nimble Monitoring

SummaryBlock Storage File Storage Hardware Health
HPE Nimble Monitoring SummaryHPE Nimble Monitoring Block HPE Nimble Monitoring FileHPE Nimble Monitoring Hardware Health

 

Monitoring INFINIDAT InfiniBox

Summary
Block Storage
File Storage
Hardware Health
INFINIDAT InfiniBox Monitoring SummaryINFINIDAT InfiniBox Monitoring Block INFINIDAT InfiniBox Monitoring FileINFINIDAT InfiniBox Monitoring Hardware Health

 

Monitoring IBM V9000

You'll have to try this one yourself, looks the same as our monitoring for IBM SVC.

 

WHAT'S NEXT?

Don't see what you are looking for here? Check out the What we are working on for SRM after v6.6 -- Updated on Apr 2, 2018 post for what our dedicated team of storage nerds and code jockeys are already looking at.  If you don't see everything you've been wishing for there, add it to the Storage Manager (Storage Profiler) Feature Requests.

 

Note: The SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates.  All other trademarks are the property of their respective owners.

Filter Blog

By date: By tag:

SolarWinds uses cookies on its websites to make your online experience easier and better. By using our website, you consent to our use of cookies. For more information on cookies, see our cookie policy.