I have a sensor set to do a simple SQL query. During a particular timeframe, there seems to be a conflict with other SQL jobs running on the database server. My sensor query is often chosen as the deadlock victim during that time, resulting in an alert. I already have it set to go to Warning on the first occurrence and then Down on a subsequent one. Is there a way for me to set the sensor to ignore the failure due to deadlock and not alert if my SQL query is the deadlock victim?
PRTG SQL query chosen as deadlock victim?
Modified on 2025-06-10 16:10:27 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Hi Mark,
Thank you for your post!
Please note that it's not possible to ignore this error message since it comes directly from PRTG and not from the target device.
As an alternative, if you know at what time the other jobs are running, you can define a schedule for the corresponding Sensor. A schedule pauses the Sensor for certain periods of time, so the Sensor only scans when no other job is running.
Best Regards,
Moritz Heller
Paessler Support Team
Jul, 2019 - Permalink