This blog is aimed primarily at those who use notifications for SAP EarlyWatch Alerts in SAP for Me. If you haven't already done so, you can find an introduction in Stay Informed About New SAP EarlyWatch Alerts You Are Interested In. In short, you can use the notification framework of SAP for Me to get notified about new issues in the SAP EarlyWatch Alert service. You can define the topics and systems you want to be informed about in in the notification settings.
This feature is available since September 2020; and as the first topics, notifications have been enabled for new decisive red alerts and new issues in the 2 billion record limit app. As an additional topic, notifications for the memory consumption of the SAP HANA index server were activated just now on 04.11.2021.
The index server is the main SAP HANA database management component; it is the most critical component with regard to SAP HANA memory consumption and must be monitored regularly. The Index Server Memory Usage of the SAP EarlyWatch Alert Service reports and forecasts the memory usage in the index server of your SAP HANA databases. If the memory consumption of the index server approaches the effective allocation limit, table unloads or even out-of-memory dumps may occur. The app gives you an overview which index servers are approaching the effective allocation limit including a prediction when the limit is reached. See also Memory Forecast for SAP HANA with SAP EarlyWatch Alert Workspace.
In detail, a notification is triggered if an index server within the filter settings of the corresponding view meets one of the following conditions:
The memory consumption is growing significantly faster than usual.
A new level of criticality is reached (there are the following levels, depending on the period until the effective allocation limit may be reached: 3 Months - 6 Months, 1 Week - 3 Months, Already reached).
The forecast is not possible for the first time due to insufficient data.
The memory consumption was regarded as critical before, is now not reaching the limit within the next 6 months.
But one question remains: How do you learn about new topics within SAP EarlyWatch Alert which are enabled for notifications? Now, you are reading the relevant blog, but this is not a sustainable solution - especially if more topics will be enabled for notifications in the future. Probably the easiest way for this would be that notifications for new enabled topics would be automatically activated - and specifically for those views in which you have already active notifications, that is, the systems, database types, or customers you are interested in. If you are not interested in the topic, you would simply have to deactivate the card representing the topic in the notification settings.
This is exactly how the notification settings are adjusted: if new cards are enabled for SAP EarlyWatch notifications, they are automatically activated for exactly those views in which active notifications already exist. In the case of the SAP HANA memory forecast, this means that if you currently have active notifications for SAP EarlyWatch Alert, the notifications for the new card are automatically activated in all views with active notifications:
Maybe you have already received one of these new notifications, and maybe you wondered why you received them. Well, you know now. Receiving a notification that you might not be interested in (and which you can easily turn off at any time) is less problematic than missing a notification for your systems that points you to a potentially serious issue.
So in the future, if notifications will be enabled for further cards in the SAP EarlyWatch Alert Workspace, you will be informed. Also, without reading a blog - just by receiving a notification if there is an issue.