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:
Max dead locks:
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.
| Parameter | Description |
|---|---|
| Active | If checked, the rule is enabled and will be processed. |
| Max deadlocks | The threshold for the maximum number of deadlocks, Use the multi-threshold syntax (e.g., G2W:1 W2M:5) |
| Auto clear | If set, the generated alarms will be automatically cleared from the console if the alarm condition is no longer met |
| Alarm tag | Allows custom text to be added to the alarm message. The %MSG% variable will contain the actual generated message and can be used, for example, as “my_prefix %MSG% my_suffix”. By default, the tag will be used as a prefix |
| Exclusive | Defines if matching object names are removed from subsequent rules |
| Alarm | Defines if alerting is active for this rule |
| Metric | Defines if metric generation is active for this rule |
| Report | If checked, this rule will be used for showing threshold and severity in the daily report |
Here is an example based on the format and the image provided:
| Active | Object Name | Max deadlocks | Severity | Aggregates | Auto clear | Alarm tag | Exclusive | Alarm | Report |
|---|---|---|---|---|---|---|---|---|---|
| true | * | G2W:1 W2M:5 | WARNING | true | false | true | true | true |
Effect : A alarm is sent if a deadlock is found and matching with “max deadlocks” since the last check