VCF Operations Diagnostics
- Brock Peterson

- 4 hours ago
- 2 min read
We introduced Diagnostics in 8.18, improved on it in 8.18.2, and re-imagined it entirely in VCF Operations 9!

In addition to Active Findings (exportable), we have Historical Findings, and the Findings Catalog. We also introduced Log Assist, the ability to upload Support Bundles to Broadcom Support for SRs.
Active Findings are based on two things: logs and properties. To trigger a log-based finding run you select the REFRESH FINDINGS button.

Log-based Active Findings will be shown as Refresh type "Manual". Property-based findings are run every four hours and will be shown as Refresh type "Auto".

The Findings Catalog will show hundreds of things we are looking for: VMSA/CVE exposure, VCF best practices, issues with known KBs, trending support issues, and more. There might be a time you choose to ignore some of these Findings and as such would like to mute them in Active Findings tab, here's how you do it.
Go to Infrastructure Operations - Configurations - Management Pack Configurations and create a new configuration file by clicking the ADD button. Name your new configuration file "diagnostics_mp_config_overwrites.json" and populate it like this. Note the "Free format" slide bar.

The Finding I'd like to mute is "VCFOperations_clusterof3to18_KB_318074", it looked like this in Active Findings.

I wanted to ignore it because in my lab I'm only running a single node Logs Cluster by design. Once I created and saved the configuration file above the Active Finding disappeared from my list of Active Findings.

If you want to mute multiple findings your configuration file would look something like this.

This is a nice way to minimize known noise in Active Findings, hope this was helpful!
Comments