Deployment Health -- database maintenance and index fragmentation

I'm getting the impression that the Deployment Health tool isn't tuned properly. I get a database index fragmentation warning on five unspecified tables so I ran reports to list any fragmented indexes. On both clustered and non-clustered  indexes nothing came up. So either reports are wrong or the deployment health is wrong.

I also had a ticket opened for Agent indications reported as a problem - since I have no Agents in this environment. Support relayed that this is a false positive. Not impressed by these potential problems not being vetted by the application.

I'm getting tons of random Problems and Potential Issues in the Deployment Health. The messages in them specifically call out failures and problems, but like you, the issue is either not actually happening or I have resolved it and the Deployment Health check still reports it. I opened a case with support and it about the equivalent of talking to a random person on the street about it. They have no suggestions other than to ignore it, which I find unacceptable. I rely on this platform to do my monitoring, so am I asking for too much by wanting to know what is causing these Health Checks to fail?

for what its worth - support told me the Deployment Health table in the database retains the information for 20 days. Either way, Deployment Health is not proving useful in regard to determine SolarWinds environment health. Hopefully this gets attention and improves in the next release post 12.5

Honestly that page just gives me headaches.   Makes more sense to just rely on the built in Orion server SAM template to keep eyes on what's going on.

This could be caused by an incorrect setting.: https://support.solarwinds.com/SuccessCenter/s/article/Default-database-retention-settings-for-the-Orion-Platform?language=en_US