# SAP HANA Alert Management Effective alert management is essential for maintaining the stability, performance, and overall health of an SAP HANA system. HANA Alert Management helps administrators stay informed through timely alerts, enabling efficient handling of system health via proactive monitoring and defined threshold settings. HANA alerts are triggered at various priority levels based on the severity of issues. SAP HANA’s internal monitoring infrastructure continuously gathers and evaluates data on system status, performance, and resource usage. Regular checks on system tables and views are conducted, with alerts generated when specific thresholds are exceeded. For instance, if 90% of disk space is used, a low-priority alert is issued; at 98% usage, a high-priority alert is triggered. Alerts are categorized by severity to help administrators prioritize their responses. The scale ranges from 1 to 4, with 1 being informational and 4 being critical. It is important to have a well-defined alert management strategy to ensure alerts are handled effectively and that critical issues are addressed promptly. Proper configuration and management of these alerts enable the maintenance of optimal system performance. ### HANA Alert Exclusion HANA Alerts can be excluded by creating alert configurations or thresholds to prevent specific alerts from being triggered. Alternatively, administrators can use the SAP HANA Cockpit or SAP HANA Studio to manually suppress alerts during maintenance or for known conditions, reducing false alarms during these periods. This allows for continued monitoring of critical alerts while excluding unnecessary or low-priority HANA alert notifications. IT-Conductor provides a simple alternative for managing HANA alerts using the HANA Alert Retriever, Threshold Override, and RegEx (Regular Expression). ### Exclude HANA Alerts Using IT-Conductor HANA Alert Retriever This method prevents IT-Conductor from retrieving specific HANA alerts based on the provided Alert ID. The excluded alert is neither displayed on the monitoring chart nor triggers notifications. {% hint style="info" %} **Note:** This exclusion is only effective for one HANA system. {% endhint %} 1. Navigate to **Dashboards** **→** **Default**. Locate the **Alerts** panel and select the HANA alert you want to exclude.

Figure 1: Default Dashboard in IT-Conductor

Alternatively, the **Alerts** page can be accessed by navigating to **Management → Monitoring → Alerts**. 2. Take note of the **Alert ID** (e.g., 106).

Figure 2: HANA Alert Details Page

3. Navigate to the relevant HANA system in the Service Grid and click **Retrievers**.

Figure 3: HANA System View in Service Grid

4. Click **Alert Retriever** from the list.

Figure 4: HANA Retrievers

5. Under the **Exclusion Criteria** section, click **Add New Row** . 6. In the **Attribute** dropdown, select `HANAAlert.ALERT_ID`. 7. Choose the appropriate operator (e.g., **=** for a single value or **in** for multiple values). 8. Enter the Alert ID (e.g., 106) in the **Value** field. 9. Click **Create** to add the entry, then click **Save** to apply the changes. You can later edit this row using **Modify Row** .

Figure 5: Modify HANA Alert Retriever

### Exclude HANA Alerts Using IT-Conductor HANA Alert Threshold Override This second approach allows for the collection and display of HANA alerts on the monitoring chart, but it doesn't trigger notifications. Unlike the first method, this one ensures data is still captured and visible for monitoring trends and severity. This exclusion method offers more flexibility. It can be applied to individual HANA systems, groups of systems, specific environments (DEV, QA, or PROD), and individual organizations within your tenant. It can also be applied globally across all systems in your environment. This granular control allows you to tailor alert exclusion to your specific needs across your entire environment. 1. Click **All Alerts** to open the **Object** **menu**, then click **Overrides**.

Figure 6: Overrides Menu Option

2. Click the override name (e.g., **HANA: High Priority Alerts**).

Figure 7: HANA Alert Override

3. In the **Object Criteria** section, click the **Add New Row** button. 4. Select `HANAAlert.ALERT_ID` from the **Attribute Name** dropdown. 5. Choose the appropriate operator (e.g., **=** for a single value or **in** for multiple values). 6. Enter the Alert ID (e.g., 106) in the **Value** field. 7. Click **Create** to add the entry, then click **Save** to apply the changes.

Figure 8: HANA Override Object Criteria

### Exclude HANA Alerts Using RegEx Regular expressions, which are powerful tools for pattern matching, can be used to exclude HANA alerts in either the HANA Alert Retriever or the Threshold Override Rule. This is particularly useful when you need to match alerts based on specific patterns or criteria. In the example below, the steps are demonstrated using the Threshold Override Object Criteria; however, similar steps can be applied when using the HANA Alert Retriever method. 1. Add a new rule to the **Object Criteria** by clicking **New Row** . 2. Select the appropriate attribute (e.g., `HANAAlert.ALERT_NAME`). 3. Choose the RegEx operator (e.g., `!regex`). 4. Enter the value that matches the HANA alert pattern you want to exclude. 5. Click **Create** to add the entry, then click **Save** to apply the changes.

Figure 9: HANA Override Object Criteria Using RegEx

{% hint style="info" %} **Note:** Regular reviews of alert configurations are recommended to determine when to revert to previous settings or disable unnecessary alerts. This helps keep the system organized and prevents excessive notifications or noise. {% endhint %} ### Video {% embed url="" %}