SAP EarlyWatch Alert

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.

 

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)

Procedure

From the sidebar, select Reporting → SAP EarlyWatch Alert tab.

The SAP EarlyWatch Alert section contains the following subsections:

Coverage

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

  • If the EarlyWatch Alert WorkSpace has received an EWA for the system within the last 14 days then it is considered to be Covered
  • If the latest EWA data received for the system is more than 14 days old but less than 90 days old then it will fall under Outdated
  • If the latest EWA data received is older than 90 days and less than 183 days or no EWA data is found it will state Not Covered
     

EWA Relevance

  • Only productive systems have been considered by default. Test (and all other) systems are filtered out by the default filter. 
  • ABAP based systems are considered for the coverage calculation (old SAP NetWeaver or new SAP S/4HANA Foundation which includes the ABAP Platform) along with HANA standalone systems (and any HANA systems that have not sent EWA at all so we do not know if they are standalone). This section does not contain JAVA or BOBJ systems. 
  • Only systems with the leading products for which SAP EarlyWatch Alert is possible are considered. You can check the system data to find the leading product via My Landscape(opens in new tab).
     

Charts and Tables

The Coverage section contains the following charts and table:

  • Coverage of SAP NetWeaver Systems – shows the systems, grouped by their coverage status. Three grouping types are possible.
    • Covered, meaning a recent EWA has been sent to SAP.
    • Outdated, meaning at least one EWA has been sent to SAP but no alert has been received recently.
    • Not Covered, meaning there has never been an EWA sent to SAP.
  • Coverage by Product – shows coverage status of SAP EarlyWatch Alert, by the number of systems per products code.
  • Coverage Detail – a table showing details of your coverage status.

 

Reports

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).


 

Charts and Tables

  • Overall Rating – shows the number of red, yellow, and green EarlyWatch Alert reports sent to SAP each week. You can customize the selections for the number of weeks to display, productive or non-productive systems, and specific ratings.
  • Overall Rating Table – shows the details of the EarlyWatch Alert reports based on the selection from the Overall Rating chart. From here you can click on the system number entries and it will take you to the system details in SAP for Me. You can also click on the Report Date entries, and it will take you to the reporting specifically to this report for this system/date.
  • EarlyWatch Alert History – This table shows the details of the EarlyWatch Alert reports based on the selection from the Overall Rating chart.
    From here you can click on the system number entries and it will take you to the system details in SAP for Me.
    You can also click on the Report Date entries, and it will take you to the reporting specifically to this report for this system/date.

Alerts

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.

Note:

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.

Charts and Graphs

  • Single Alerts Rating – displays the number of decisive red, red, and yellow alerts found in the EarlyWatch Alerts in each week. You can customize the graph regarding timeframe, productive/non-productive, and ratings.
  • Single Alerts Table – shows the details of the EarlyWatch Alerts based on the selection from the Single Alerts chart. You can see how many of each alerts (decisive red/red/yellow) are found in the corresponding system’s EWA report. From here you can click on the Reporting Date (only for an EWA from the past 7 days) and it will take you to the EarlyWatch Alert Solution Finder specifically to this report for this system/date where you can see the findings from the corresponding report for the selected rating.
    Only the latest EWAs that are dated from the last 7 days will have the option to select the Reporting Date (others will be greyed out) to jump into the EarlyWatch Alert Solution Finder as the Solution Finder tool only keeps the last weeks EWA alerts available.
    Note:  The number of alerts returned in the EarlyWatch Alert Solution Finder may be smaller than the number in the Enterprise Support reporting cockpit (and in the PDF version) as the Solution Finder combines like alerts.

Active Users

The Active Users(opens in new tab) section displays an overview of the active users, reported by the SAP EarlyWatch Alert.

 

Charts and Tables

  • System Growth by Active Users – shows the top 5 productive systems by Active Users of the last SAP EarlyWatch Alert report. The top 5 systems are shown in the graph but looking at the table on the right allows you to see information from all the systems.
    For the top systems by Active Users, only ABAP based systems are analyzed. User activity is measured in the workload monitor. Only users of at least medium activity (more than 400 dialog steps per week) are counted as Active Users, see the section 'workload by users’ in the EWA report.
  • System Growth by Active Users Table – shows details of active users.

Database Size

The Database Size(opens in new tab) section displays an overview on the database size, reported by the SAP EarlyWatch Alert.

 

Charts and Tables

  • System Growth by Database Size – This chart shows the top 5 productive systems by Database Size as of the last EarlyWatch Alert report. The top 5 systems are shown in the graph but looking at the table on the right allows you to see information from all the systems.
  • System Growth by Database Size Table – By clicking on the More Information in the table on the right you will get a new window that will show you the data volume graph as found in the EWA Dashboard.

Consumption

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. 

  • EWA Workspace – this is just a call to the workspace in general (note, if the customer has personalized and removed the card ‘top systems’ then this is no longer counted).
  • EWA Viewer – is when the customer has entered into the EWA Viewer. This can actually happen in many ways, for example, in the EWA dashboard of a system (selected a top system), by selecting a section of the donut chart for overall rating, or even just entering the EWA Viewer directly from the SAP ONE Support Launchpad. 
  • HANA Memory Prediction – is when the customer has clicked on the „main memory SAP HANA“ card.  
  • EWA Dashboard – is when the customer selects a single system from the Top Systems card in the workspace. 
  • EWA Performance Trend – is when the customer clicks a bar of the chart in the card Top Deviation in Response Time. 
  • EWA 2 Billion Record Limit – is when the customer clicks on the card 2 Billion Record Limit. 
  • EWA Number Range Forecast – is when the customer clicks on the card Critical Number Ranges.
  • EWA Solution Finder – is when the customer enters into the EWA Solution Finder tool.  
     

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.
     

Charts and Tables

  • Visits – shows you if the customer has visited the EWA Workspace along with the key cards that they explored.
  • Notifications – Customers can set up notifications for a variety of applications (License Keys, SAP Notes, SAP HotNews…).  One of these notification settings is associated with the SAP EarlyWatch Alert Workspace where one can set up to be notified regarding critical issues being reported on in the workspace.