Required Authorization
In addition to Display Support Situation Reporting for the dashboard, this section users require either:
- Service Reports and Feedback (customers)
or
- Service Reports (partner)
The SAP EarlyWatch Alert(opens in new tab) section contains information received through SAP EarlyWatch Alert services, structured into various subsections. The SAP EarlyWatch Alert service identifies potential problems before they affect your business. It should be scheduled weekly on all productively-used systems. For more information check out the SAP Support Portal page(opens in new tab) or KBA 207223(opens in new tab).
The SAP EarlyWatch Alert section is based on data in the SAP EarlyWatch Alert Workspace application(opens in new tab), which shows results from recent SAP EarlyWatch Alert service reports across all systems. Therefore, access to SAP EarlyWatch Alert data in the Reporting section requires the same authorizations as the SAP EarlyWatch Alert workspace.
In addition to Display Support Situation Reporting for the dashboard, this section users require either:
From the sidebar, select Reporting → SAP EarlyWatch Alert tab.
The SAP EarlyWatch Alert section contains the following subsections:
The Coverage(opens in new tab) section provides an overview on the SAP EarlyWatch Alert (EWA) enablement of your productive SAP ABAP systems and SAP HANA standalone systems.
The EWA coverage ratio is calculated by the number of systems that sent EWA data, divided by the sum of the number of systems that sent EWA data and the number of systems that did not send EWA data, but with EWA relevance.
Sent EW Data Definitions
EWA Relevance
The Coverage section contains the following charts and table:
The Reports(opens in new tab) section provides an overview of the SAP EarlyWatch reports sent to SAP.
If you send your SAP EarlyWatch Alert data to SAP, reports can be viewed the SAP EarlyWatch Alert Workspace(opens in new tab).
You can also go to the SAP EarlyWatch Alert Viewer from the SAP ONE Support Launchpad(opens in new tab).
Inside each SAP EarlyWatch Alert(opens in new tab) report you find all the alerts in an overview table. These alerts highlight key findings that should be analyzed to determine if critical to your system. The alerts are rated either Red or Yellow depending on severity of the finding.
A few Red alerts are deemed critical enough to cause the rating on the entire EarlyWatch Alert to be Red. These are indicated as Decisive Red and in turn, are the ratings that caused the EarlyWatch Alert to get an overall red rating. If a report has only Red and Yellow ratings then the overall report will be rated Yellow.
Because of the fundamental importance of security alerts, we want to be sure customers are keeping an eye on through the EarlyWatch Alert reports. But due to the sensitivity of the data we do not show the information in the customer insights cockpit. Instead they are displayed in SAP EarlyWatch Alert Workspace and protected by an additional authorization. Only dedicated S-users can request this authorization. Go to the blog(opens in new tab) to discover more.
The Active Users(opens in new tab) section displays an overview of the active users, reported by the SAP EarlyWatch Alert.
The Database Size(opens in new tab) section displays an overview on the database size, reported by the SAP EarlyWatch Alert.
SAP EarlyWatch Consumption(opens in new tab) is key to understanding if the customer is using this important tool showing visits to the tool and the different cards of the tool along with if the customer has set up personal notifications.
The key areas where customer visits are tracked are listed below. For details on what the customer can see in these areas, please visit the EWA Workspace directly and use the help provided there, here we are just focusing on the usage metrics.
The key notifications that you can turn on are for the following:
Decisive Red Alerts – decisive red alerts are those red findings in the EWA report which are deemed critical enough to make the rating on the entire EWA red.
2 Billion Record Limit for Critical Tables – HANA tables are restricted to two billion rows per partition, so in case a table is approaching this limit a notification can be sent.
2 Billion Record Limit for Solved Tables – Once a HANA table that was approaching the two billion rows per partition has been resolved a notification can be sent.
SAP HANA Memory Forecast - 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. This notification will trigger when index servers are approaching the effective allocation limit.