This sounds like a similar problem i had with data from Azure. The Azure checks are extended with the behavior that missing data don’t lead to an UNKN state but that the service goes stale.
yes, that would be very helpful. With v2.0.0p1 we still have that issue as well. It’s pretty annoying as we have around 450 data sets per AWS account and all the time there are some which are going into UNKN randomly.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.