Delay for alerting on DBSS Usability Connection Availability up to 30 minutes (4307642)

The database collections do not fail, but rather time out due to a lack of response from the monitored host.

The usability collection frequency is 5 minutes. This collection waits in the queue while each of the other collections are being executed. Since each running collection is hangs for one or more minutes before it receives the timeout that the network connection (server) is unavailable. When there are ten collections in the queue, and the timeout is set higher this can result in increased (e.g. 20 minutes) delays.

Reduce the network timeout setting in the Agent Status Properties to reduce the number of seconds before the failed network connection ends the collection run. This however could have negative effects on the running of other collections if there are network performance issues.

This is by design because when a server is no longer available, all of the database agent collections will begin to fail. The user should begin encountering numerous collection status errors. Reducing the network timeout settings to an very low setting would permit the alarms to fire sooner by in turn could have negative effects on the success of other queries completing if there network performance issues.