This monitor is meant to detect when the database is reaching its limits in processing capabilities. Such situations will impact response times for programs and users. It will check database CPU and threads usage.

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 the maximum total CPU usage ratio and the minimum idle time ratio for threads of each pool.

Total CPU usage:

• Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:90 W2M:95 M2C:98 (Green To Warning, Warning To Major, etc…).
• An alarm of the corresponding severity will be sent if the CPU usage is over threshold. Set 0 in the field if unused

Thread pool idle ratio:

• For each thread pool, this monitor will collect the average idle ratio of its threads
• If the idle ratio is below a threshold, and alarm can be sent.
• Use the multi threshold syntax to set multiple severity levels.
• The average idle ratio is computed between two checks.
• You can then set a filter on the thread pool name if you need to set a specific rule for it.

Computing method:

• CPU and idle ratio computing is based on two readings: The current one and the one from the last check.
• If the monitor runs every 15 minutes, CPU and idle ratio will be the average of the last 15 minutes.
• Use the schedule time to increase or decrease the average period.

Rules order:

• Rules are processed following their order in the table:
• One given pool can only be processed once, it will be ignored by subsequent rules.
• Therefore you MUST define specific rules (for a give pool) before general ones (for all).

Effect : A WARNING alarm is sent if CPU usage is over 90% (MAJOR if over 95%). A WARNING alarm is sent for every pool of threads with an idle ratio lower than 60% (MAJOR if lower than 40%)