====== MAXDB performance======
===== Purpose =====
  Database performance must be monitored closely in order to detect any drop and 
  avoid blocking situation for your applications and users
===== Configuration hints =====
  * Use the configuration table to setup monitoring rules on available performance metrics
====Performance metrics====
  * You can create a rule for a selected list of metrics:
    * DEADLOCKS
    * DEADLOCKS_PER_TABLE
    * USED_SPACE_IN_FILES
    * DATA_USED_SPACE
    * LOG_USED_SPACE
    * DATAFULL
    * CACHE_HIT_RATIO
    * CHECK_ADMIN_STATE
  * Set the ''//Threshold//'' field with the appropriate value
  * If the threshold is reached, an alarm will be sent
  * You can use multi threshold syntax, otherwise the ''//Severity//'' field will be used to set alarm severity.

===== Surveillance table =====
^Parameter^Description^
^Active|If checked, the rule is enabled and will be processed|
^Performance metric|The metric to monitor|
^Threshold|The maximum value for the selected metric|
^Severity|Defines the severity of the alert generated (unless multi threshold syntax is used)|
^Auto clear|If set, the monitor will CLEAR any previous alarm if the conditions of those alarms are not true anymore|
^Alarm tag|You can define some text to use as a prefix of the alarm message generated by the current rule|
^Alarm|Defines if an alarm has to be generated for the given rule|
^Metric|Defines if a metric has to be generated for the given rule|

===== Generated metrics ===== 
 
^metricId^metricUnit^metricTarget^metricDescription^
|MAXDB_DEADLOCK_COUNT|count| |The number of deadlocks|
|MAXDB_USED_SPACE_IN_FILES_PERC|%|FILE|The used space per file|
|CACHE_HIT_RATIO|%|CACHE|The hit ratio per cache|
|DATA_USED_SPACE_PERC|%| |The space used by DATA|
|LOG_USED_SPACE_PERC|%| |The space used by LOG|
|ADMIN_STATE|boolean| |Sends 1 if admin state is ON|