vbulosity is a blog about VMware Software Defined Datacenter (SDDC) with emphasis in Cloud Operations Management. VMware vRealize Operations Manager or vROps/vR Ops formerly known as VMware vCenter Operations Manager or vCOps/vC Ops will be the main topic.
Most new vROps users are intimidated by vROps Policies as there are literally hundreds of settings that can be tweaked and customized. From Badge Threshold sliders and a myriad of checkboxes, to radio buttons and dropdowns, there is an endless stream of what seems like redundant settings. The reality is that there are only a handful of settings that should be initially tweaked for most use cases. In this blog post, I will review the most common Policy settings that should be modified in order to get the most value out of the solution and save your sanity. This by no means will be a comprehensive guide to vROps Policies, but it should have enough to get you started on the path to successfully managing your environment, instill some confidence, and whet your appetite to do more.
When you edit vROps Policies, you are presented with a screen that has a ton of settings and expected to know exactly what to customize to meet your unique organization's needs. Not to worry, I'll cover …
Since the EPOps vCenter Monitoring Dashboard is one of the most popular posts on the blog, I thought it would be a good idea to update this highly demanded dashboard to work with multiple vCenters. A lot of sizable enterprises out there have multiple vCenter instances with thousands of hosts and tens of thousands of VMs. Also, with the introduction of vSphere 6, more customers have begun their migration journey away from Windows-based vCenter servers to vCenter Server Appliance (VCSA) and everything in-between, including a mix of both solutions. Since vROps enables you to have a unified single pane of glass view across your entire environment regardless of locations or versions, you can leverage it to create a dashboard to keep an eye on all of your vCenter servers. This can include both Windows and VCSA versions of vCenter, as well as SSO and PSC if they have been separated out. Heck, you can even include the MS SQL server hosting the vCenter database if you want.
As I mentioned in my previous vROps Self-Monitoring Dashboard post, you need a way to get notified when vROps self-monitoring alerts get triggered. This way you don't have to keep staring at the dashboard all day and can rest assured that if something goes awry you will find out. Even though vROps is deployed as a Virtual Appliance (VA) in most environments, it is important to remember that under the hood it is still just another application with services running in an Operating System. Therefore, just like any other application, it is susceptible to failure at some point. In this post, I will go over how to setup simple email notifications for vROps self-monitoring alerts if there is an issue with one of the vROps objects such as Cluster, Nodes, or one of the application services.