Allow configuration -> monitored servers to have configurable retries and wait timeouts.
We have a vpn between our sqlmonitor and several of our sql servers. I'm not sure how often sqlmonitor will retry or wait between retries when that vpn is unavailable due to any number of reasons. When the monitoring becomes unavailable, I would like to be able to allow sql monitor to retry every X seconds for up to X hours or X times as it attempts to reconnect.
Matthew Gerrior
shared this idea
As of SQL Monitor 5.0, the retry logic is much more robust, and most users have reported no more issues with SQL Monitor reconnecting
-
P Curd
commented
To avoid the DoS problem, perhaps make it configurable so that those of us that don't have DoS detection can be more aggressive? Even a check per hour would be very useful for those problems that happen when a 3am reboot occurs.
-
Priya Sinha
commented
Thanks a lot Matthew for your feedback.
The current SQL Monitor 2.3 behaviour is that if a particular data collection method doesn't work for some reason .. the monitoring still continues. E.g. if remote registry is stopped then also monitoring with continue. This is show you appropriate error on the Manage Monitored Entity page. You will also get a data collection error alert after 2 minute.
But if for some reason, when Monitor tries to connect and if gets an authentication error then we stop monitoring completely. The reason for this behaviour was that in case one has intrusion detection system in their environment then it could result into denial of service attack.
When VPU is unavailable, do you get authentication errors?