It is my sincere privilege to announce General Availability (GA) of Virtualization Manager (VMAN) 6.1. This release of VMAN significantly extends the capabilities of the integration that was delivered with SolarWinds NPM and SAM in VMAN 6.0. One thing that we've consistently heard from customers is that you want to see end-to-end in your environment, from Applications to VM's and through the rest of the virtual infrastructure, in a single pane of glass. 6.1 is one more step in pursuit of that goal. Without further ado, let me introduce you to the new features available in this release (links take you to information covered in the Beta blog posts):
The team wanted to make sure you could get up and running with the integration as quickly and painlessly as possible. This Wizard is the culmination of all the experience we've gained of how synchronization between these two products can go awry. With the new release, you can stop worrying about troubleshooting the integration and focus on troubleshooting problems in your IT environment.
The features we're delivering in the integration are built around this concept of the "vNode." More than a cute name, it represents a significant departure from how the integration was delivered in VMAN 6.0. In 6.0, in order to see data for VM's you had to manage all of your VM's as Orion Nodes, which basically incurred a "double-licensing tax." Well, no more. With 6.1, you can see the VMAN data in the integration without also managing your VM's as Nodes. These VM's can also be managed as Nodes if you need NPM or SAM specific features, like Asset Inventory or Hardware Health, but it's no longer necessary in order to realize the benefits of the integration. With 6.1, only the top-level datasource (the entity we poll data from), need to be managed as Nodes (e.g. vCenter for VMware or a Hyper-V Host for Hyper-V). vNodes have their own resources and also allow us to deliver features like Hyper-V Clusters, Account View Limitations, and Alerting and Reporting on VMAN entities in Orion.
The integration now allows using Orion's Account View Limitations, a feature required in order for Virt Admins to complete the delivery of the private cloud to their internal customers. Limit at the vCenter level, the VM level or anywhere in between to limit views to only what consumers of the private cloud need to see.
Following in the footsteps of SAM 6.0 and NPM 10.7, VMAN 6.1 has extended the baseline threshold capability to the virtual environment. No more need to play psychic in setting static thresholds across your virtual environment - let VMAN do the hard work for you.
Now you can build reports on your applications and Guest OS status information right along side reports on your virtual infrastructure, all from the same interface.
Significant improvements to data collection and processing on the VMAN virtual appliance (vApp)
The engineering team has done a fantastic job in making the necessary changes to make VMAN truly an Enterprise-class monitoring system. With a properly sized server and a tuned appliance, VMAN is now ready to monitor even the largest VMware and Hyper-V environments.
No more applying new keys when you renew your Maintenance!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.