Deadlocks can significantly reduce the performance of the applications and the response time for the users. This is usually reflecting a blocking situation which can last a long time.
It is therefore very important to detect deadlocks and act rapidly to resolve them if necessary.

Surveillance table:

• This is a table of rules that you can use to configure and customize the configuration.
• Each line of the table will define a rule of monitoring.
• You can combine multiple rules to cover different cases.
• Within a rule, you can configure a threshold for the number of deadlocks to reach before sending an alert

Max dead locks:

• Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:1 W2M:5 (Green To Warning, Warning To Major, etc…).
• An alarm of the corresponding severity will be sent if the number of deadlocks is reaching the threshold.
• Set 0 in the field if unused

This monitor will look for deadlocks that occurred since the last check. It will cope with server restart up to a period of 2 hours of down time.

Here is an example based on the format and the image provided:

Effect : A alarm is sent if a deadlock is found and matching with “max deadlocks” since the last check