The "sqlserver" probe generates alarms if query times out or profile fails to execute in scheduled time interval.
Explanation of sqlserver probe timeout fields to help get rid of timeout failures/ 'query timed out' alarms:
Here is a complete explanation describing all of the timeout fields in sqlserver profiles which can help get rid of any timeout alarms/query timeouts/failures:
1. Heartbeat - Defines the interval at which all profile checkpoint schedules will be tested and trigger eventual checkpoint execution.
2. Check Interval - Default value for check interval in the profile.
3. Profile Timeout - Defines the maximum processing time for all checkpoints in the profile.
4. SQL Timeout - Every checkpoint query runs asynchronously.
5. Delay Threshold -
If you are getting alarms for
"Profile <Database Server>, failed to execute in the scheduled time interval, delayed by <seconds> seconds", it means that your profile is taking more time to get executed then the described heartbeat interval.
For example, if the profile has configured as follows:-
You are getting the alarm because the Profile would be getting executed say 2 mins (1 min more than scheduled interval i.e Heartbeat) which are within the profile timeout limit, but more than "Delay_Threshold" limit.
***The query timed out! alarm comes when the SQL Timeout in the profile is less than how long the query takes so please increase this value to some appropriate value.
If you have lots of data in the database then a checkpoint will take more time which can lead to high profile execution time and hence result in timeout alarms.
You can configure the remaining timeouts based on the above explanation and the alarm you are getting.