As an administrator, using the Alerts app, you can monitor the status of your SAP HANA Cloud database instance. With the Alerts app, you're alerted to critical situations, for example: a disk is becoming full, CPU usage is reaching a critical level, or a server has stopped.
The internal monitoring infrastructure of the SAP HANA database continuously collects and evaluates information about status, performance, and resource usage from all components of the SAP HANA database. In addition, it conducts regular checks on the data in system tables and views, and when configurable threshold values are exceeded, it generates alerts to warn you of potential problems. The alert priority and threshold values can be customized as desired, so that the priority of the alert reflects the severity of the problem. For example, if 90% of available disk space has been used, a low-priority alert is generated; if 98% has been used, a high-priority alert is generated.
SAP HANA Cloud Central – Alerts app
To open the alerts application in SAP HANA Cloud Central, choose the Alerts (1) link in the navigation panel.
In the Search (2) area, the alert severity is, by default, filtered to show only "Error" and "Warning"; all other filter options are left empty. The Instance filter is empty by default, resulting in all instances being displayed in the table. You can filter, sort, and view details in the search area as needed.
By default, the Alerts (3) list displays all "Error" and "Warning" alerts, that occurred in the past 24 hours. The columns shown in the Alerts list, display the following information:
- Severity - Indicates the importance of the alert and how quickly action needs to be taken. The following categories of severity are possible:
- Error - Immediate action is required to mitigate the risk of downtime, data loss, or data corruption. These issues are critical and need your full attention to prevent system failure.
- Warning - Short-term action is required (typically within a few hours or days) to mitigate the risk of potential downtime. These issues are less critical than high alerts but should not be ignored.
- Notice - Medium-term action is required to mitigate the risk of future potential downtime. You should plan to investigate and resolve these issues in a timely manner as part of your regular maintenance schedule.
- Information - Action is recommended to improve system performance or stability. These alerts are for general awareness and typically do not indicate an immediate problem, but offer opportunities for optimization.
- Start Time - Indicates the time that the alert was triggered.
- Instance - Which instance the alert is corresponding to.
- Instance Type - The specific type of database instance.
Selecting an alert will show additional information like a detailed description and a recommended action.