This weekend, we had a SQL server instance with some network problems.   I received countless email notifications that the Biztalk Group services on the Biztalk server were down followed by a clear message 1 min later, and then another down notification.

 

The Biztalk services by necessity are configured to reconnect to the SQL server, should there be a disruption, every 1 minute.  The notifications were valid, but I'm wondering if there is some means to modify this parituclar windows service, in order so that, it not be determined "clear" until the service has remained up for >1 minute? 

 

This particular Biztalk environment will go into production in a couple weeks, and I will come up with a better means to monitor, however the windows service is a good thing to look at, but for this particular service I need some threshold options, as mentioned above.  It is normal for it to start up every 1 minute to try to talk to SQL, however until it remains up for >1 minute, it is still a problem.  I would like to get rid of the erroneous clear notifications in this instance.