vRealize Operations Manager – Utilizing Action Buttons
The latest iteration of VMware’s Operations Manager was released in late 2015. Along with the new branding (moving from vCenter Operations Manager [vCOps] to vRealize Operations Manager [vROps], the new version (v6) included many impressive new features. In my opinion, one of the most impressive features of vRealize Operations Manager 6 is the ability to remediate issues straight from vROps without having to open the Web Client/Thick Client to fix each problem. Actionable features such as this will assist in the product moving from being viewed as a monitoring-only solution to more of an operational management product. With this release, the product can monitor the environment, suggest a solution, and provide a way to resolve it with the click of a button. *Note that you could do some automation in previous versions but it required the integration of vCenter Orchestrator.
For example, if a VM is experiencing CPU stress due to insufficient CPU resources, vROps will trigger an alert for this particular VM. This can be seen on the home page of vROps:
After drilling down to the individual VM’s alert you are presented with all the normal details, including graphs and suggested resources to satisfy the VMs workload. A new addition to this alert is the ability to remediate the problem straight from vROps by a simple button.
As shown above, the suggested number of vCPUs to add for this particular VM is 1. To quickly apply the recommendation, you can click the Action button highlighted above. A confirmation box will display, allowing you to customize the number of vCPUs to add (or memory if you’re adjusting RAM), select options to allow vROps to Power Off the VM if needed or take a snapshot.
By the way, if you have Memory/CPU HotPlug enabled for your VM and the guest OS is supported, you can add the resources without shutting down the guest.
Once you select the desired options, vROps will make the requested changes for you. As shown below, vROps utilized my service account “svc_vcops” to access vCenter, initiate guest shutdown, reconfigure the VM with selected changes, and power it back on.
As you can see from above, this is a very convenient feature built into vROps. More task-based features would be great to see in future iterations of vROps. Expanding a VMDK and then doing an extent in Windows would be a huge time saver as well.
If you don’t see the Action buttons highlighted above, you’re not alone. Check out this post for more information.