Diagnostics Findings are derived from vCenter, ESXi, and vSAN events, properties, and product log data that help identify potential problems or informs you about existing issues in your environment.
docs – What are Diagnostic Findings
From the point of view of some customers, it’s not so bad that Skyline Advisor is EOL and there Aria Operations 8.18 released Diagnostic, because the cloud is still the devil’s work anyway – especially if you want to hand over the data. But for many it was still not very pleasing, because not only the Findings but especially the Log Assist was a pleasing topic, especially for my customers. Why copy log files several times before you have them somewhere where you can copy them to the network when you can send them directly via Log Assist? Aria Operations Diagnostic does not solve this problem, but it does return the findings. So quickly updated to 8.18 which included the Findings functionality / dashboard and – nothing. No findings are displayed. Only an “Overall Findings 0”. I have not only noticed this with my customers, but also heard it from other TAM colleagues and noticed it in various home labs. But why is that?
First of all. It’s not mention that there is anything wrong. Most of the customer looking at the Dashboard and thing „that’s not possible, we have 100 or 1000 Hosts and much more VMs – there must be a finding“ :-). but you should not forget that „For the initial release of Diagnostics for VMware Cloud Foundation we are releasing a subset of the Skyline Advisor Property based findings and a subset of the Skyline Health Diagnostics log based findings.“ [Diagnostics for VMware Cloud Foundation 5.2 (KB: 371661)]
There is a KB Article named Diagnostic for VMware Cloud Foundation 5.2 (371661) which include an Overview which Findings are already included in 8.18.
Update 2024-11-28
There are new Findings included in 8.18.2 (Release Notes)
With this Update I got my first Finding.
But let’s be sure and check the requirements.
Diagnostic requierements
Requierements for the Findings:
- Verify that you have installed VMware Aria Operations for Logs.
- Verify that you have configured VMware Aria Operations for Logs in VMware Aria Operations.
If the connection to the vCenter is still missing because the whole environment is freshly set up, then we would see the error message at the bottom left, as shown here in Figure 2, that there is no inventory. After connecting the vCenter in the Operations Appliance under “Administration > Integrations” (KB 338384), the error message disappears and the vCenter appears.
Operations for Logs is also listed as a Requirement. If this is not installed or the integration of Operations for Logs has not yet been configured in Operations, you will see the error message above the Overview (Figure 3) “To fully utilize the capabilities of the Diagnostics feature, first install Operations for Logs and then configure it in VMware Aria Operations.” Here is the official doc: How to configure Aria Operations for Logs in Aria Operations
If these two error messages do not appear and we still have a Finding Overall 0, it is not because requirements are missing. 🙂
Which Findings are already included
Appendix
- If you would like to nominate a Findings or Idea for Diagnostics please do so under the Feedback feature in the vCenter UI. There is also a Link in KB 371661 with the description how to give Feedback.
- Also a good Overview with deeper Information about „How Diagnostic Work“ are included in What is Diagnostics for VMware Cloud Foundation.
- And there are a lot oof points in the KB: Questions and Answers for Diagnostics for VMware Cloud Foundation (375104)