We have 2 physical SQL instances and a cluster (virtual) in one of our networks, updates for those had to be done and they required a server restart. While this maintenance was done, all those sensors were paused, after the maintenance was completed, the sensors were restarted and the "disk space" sensors from the virtual SQL Cluster were showing under error state with the following log "Drive not found (code: PE013)"
Since the refresh of them didnt seem to help, i went ahead and added new sensors for the "disk space" and they all started with no errors.
Do you have any idea why this happened? and is this a process that i will have to do everytime when new updates have to be installed? or do you have some idea on how to avoid this behavior?
The sensors that didnt respond after the restart are still paused in case there is something to fix them, since we need that information for reports in the future.