Metrics install automatically if you have Redgate Monitor installed.
If you are using Redgate’s SQL Server monitoring tool, Redgate Monitor, you can instantly install and run this metric on your servers.
Connection timeouts can be difficult to troubleshoot. It’s sometimes not even apparent that a timeout has occurred. However, the connectivity_ring_buffer_recorded Extended Event can show that this has happened. This is a debug event within Extended Events, so some caution is necessary in its use. Microsoft can change the debug events without warning.
You can use SQL Monitor to see that a connection had a timeout. In order to then troubleshoot the issue, you will need to look at the information captured by the Extended Event session defined below.
Metric definition
Name
Detecting Connection Timeouts
Description
You can use SQL Monitor to see that a connection had a timeout. In order to then troubleshoot the issue, you will need to look at the information captured by the Extended Event session defined below.
The T-SQL query that will collect data
Instances to collect from
Select All
Databases to collect from
master
Collection frequency
30 Minutes
Use collected or calculated values
Leave the Use a calculated rate of change between collections check box unchecked
Metric collection
ENABLED
Alert definition
Alert name
Application Connection Timeout Has Occurred
Description
Raise an alert when the metric value goes
above the defined threshholds
Default threshold values
High: | |
Medium: | 1 |
Low: |
Raise an alert when the threshold is passed for
1 time collections
Alert is
DISABLED