How does the "DBSS - Lock Timeout Rate" rule work? (4308173)

The "DBSS - Lock Timeout Rate" rule is a multiple severity rule set to be triggered when new data is pushed to the FMS from the monitored host (most of the database cartridge and other rules are defined similarly)

This rule has been defined to fire warning alarms for values greater than or equal to 5.

This means that the rule has 2 severities:

• 0 - 5 = Normal severity
• 5 - infinity = Warning severity

Each time data is being pushed to the metric "lock_timeouts" the rule determines which severity the value of the metric belongs to.

If the severity has changed since the last time the rule was calculated, an alarm is fired. Note that the normal severity is represented by no current alarms, and if an alarm exists it is cleared when the timeout is resolved.

Information on how the Lock Timeout Rate is calculated can be found in KB 89495.

To investigate locks, and to understand the origin, we recommend using the “Lock analysis” Solution by using “Performance Analysis” tool, which completes Foglight's monitoring capabilities.
The Lock Analysis allows you to review historical data on blocking lock scenarios, including details on the database, object, lock type, blocked SQL statements and the blocking SQL.
With the utility completely integrated into all Performance Analysis dashboards, you can fully understand the dynamics of blocking in your environment and how to resolve concurrent issues.