Skip to main content
Question

Yes No Dashboard, is there a better want to manage the YES/NOs

  • September 15, 2026
  • 0 replies
  • 0 views

jamesramsden
Forum|alt.badge.img+1

We use the Dynamic App inspector report to find devices that have fallen out of monitoring for a long period of time, which is mostly due to an issue on the device. 

Any device that has an object with this would be one we’d need to look into:

Found = YES / Collect = NO

 

The trouble we have is that there is too much data that doesn’t require attention. For example SQL clusters, where Databases have moved to a secondary, but the DBs are still present on the primary but you cant read them, so this generates a YES found NO collect. 
And other DAs, where features are not enabled, but the DAs will align, like DB mirroring which can be disabled. 

Azure is a big one, where subscriptions are not including certain data sets, but the DA still attempts, and you end up with a YES found and NO collect. 

With so many devices, under Azure, ACI, Netapp for example, this data set is massive hard to find what is truly an issue sometimes. 

 

I’m looking to see if there is a better way to manage the YES/NO devices. 

Thanks