Is your enhancement related to a problem? Please describe

The implementation for isWatching used to be broken. The fix, however, resulted in isWatching very often reporting transient disconnection errors that are automatically recovered from. People relying on isWatching to asses the health of their operator therefore now see lots of unhealthy "situations" in their monitoring. While it is possible to configure the health probe to not trigger an unhealthy state without reaching a given failure threshold, error/warning messages still occur when an informer gets transiently disconnected.
It would be therefore useful to be able to configure the isWatching behavior to provide a threshold mechanism as well which would only trigger the negative response if the disconnection persisted over a configurable number of probing over a configurable interval of time.

Describe the solution you'd like

Provide informer configuration to specify a threshold interval and maximum number of attempts before a negative response is returned.

Describe alternatives you've considered

No response

Additional context

No response