====== Alerts ======
  This monitor will collect the current alerts from HANA statistics engine.

===== Configuration hints =====
  * By default, this monitor will generate an alarm for each collected HANA alert matching the minimum severity settings, set to LOW by default.
  * Use the configuration table to create specific monitoring rules such as:
    * Exclude a particular host
    * Implement specific severity mapping
    * Manage specific alert id.

  * Any HANA alert which is not matching any filter of the table will trigger an alarm.
  * You can change that behavior by switching **Unmatched alerts** settings to **REJECT**.
  * In that case, only HANA alerts matching table filters will trigger an alarm.

**Alarm severity mapping:**
  * Use the alarm mapping table to modify severity mapping.
  * You can create a mapping for a specific HANA alert.
==== Default severity Mapping ====
^ HANA alert ^ Generated severity ^
| ERROR | CRITICAL |
| HIGH | MAJOR |
| MEDIUM | MINOR |
| LOW | WARNING |
| INFORMATIONAL | INFORMATIONAL |

===== Configuration =====
==== Atomic fields ====
^ Parameter ^ Description ^
^ Auto clear|If checked the alarms will be cleared if the alert is not present anymore in the statistics engine |
^ Send metadata| When active, this will send collected alerts as metadata to Redpeaks Cockpit |
^ Minimum severity | The minimum severity of the alerts |
^ Unmatched alerts | How to handle unmatched alerts: PROCESS, REJECT |

==== Configuration table table ====
^ Parameter ^ Description ^
^ Active | If checked, the rule is enabled and will be evaluated |
^ Host | Filters alerts associated to this specified host |
^ Alert id | Filters on a specific alert id |
^ Min rating | Filters alerts with a rating greater than or equal to this value |
^ Required rating | If not set to 'disabled', the alert must have exactly this rating to be processed |
^ Auto clear | If active, the generated alarms will be cleared automatically when the corresponding HANA alert will be cleared |
^ Use index | If active, the index of the HANA alert will be used in generated alarm id, making it unique |
^ Alarm tag | Sets an arbitrary tag for alarms generated by this rule. It can then be used for filtering in alarm rules |

==== Rating mapping table ====
This table allows you to define custom mappings between HANA rating and Redpeaks severity per alert ID

^ Parameter ^ Description ^
^ Active  | If checked, the mapping is active | 
^ Alert id | Alert ID this mapping applies to  | 
^ (IN) HANA Rating | The HANA rating to match (e.g., HIGH, LOW, etc.) | 
^ (OUT) Redpeaks Severity | The severity to assign when the above rating is matched.\\ If set to 'disabled', matching alerts are excluded  | 

==== Notes ====

  * If both **Min rating** and **Required rating** are set to ''disabled'', alerts matching the rule are **excluded**
  * If **Required rating** is active (i.e., not ''disabled''), the alert **must exactly match** the specified rating to be processed
  * If **(OUT) Redpeaks Severity** is set to ''disabled'', all alerts matching the specified **(IN) HANA Rating** will be **excluded**
  * To filter on a specific **unique** HANA alert ID, use the format ''^X$'', where ''X'' is the alert ID \\ **Example:** \\ Use ''^7$'' to match only alerts with ID **7**