[24 Feb 2018 update: if the dashboard “VM Patching” loads slow, remove the Forecast column from the “VMs with high CPU utilization” list]
First, thank you for the overwhelming response on the Spectre Meltdown monitoring dashboards that I created. Glad that it’s useful.
Technically, they are all simple dashboards. They do not leverage powerful features of vRealize Operations. In fact, some of you have created your own dashboards. That means you can also modify my dashboards after you import them. You need to update the Build Numbers to reflect the changes in VMware security recommendation. My dashboards are not meant to be the authority of which builds you should have. It was correct at the time of published, but I was told there was an update to the build numbers. So you need to update the filter.
Follow these 3 screenshots on how to do it.
This screenshot 1 shows that there are 3 filters used in the View widgets. To update the widget, just click as shown.
You get the screenshot below. A dialog box pop up. Wait for it to load. Click edit.
To modify the filter, follow this last screenshot.
That’s all you need to do to update the filter. I shared that they are just simple dashboards. So what does powerful one looks like?
Here is one idea. Your CIO care more about applications. An “Application” spans multiple tiers. A tier has multiple VMs. These “Applications” run >100s different software, but consumes the same underlying infrastructure. Since the patch may cause performance and capacity problem, how do we monitor across >100s applications?
For that, you can refer to this.