EarlyWatch Alert

Introduction to Pro-Active Monitoring with SAP EarlyWatch Alert

SAP EarlyWatch Alert is an automatic service monitoring the essential administrative areas of an SAP system. Alerts indicate critical situations and give solutions to improve performance and stability.

SAP EarlyWatch Alert is most effective when activated for all SAP components in your solution. It is covered by your maintenance agreement with SAP with no extra charge, and it is a technical prerequisite to perform other remote delivery services, like SAP EarlyWatch Check or SAP GoingLive Check. It gives an overview on performance/availability KPIs and alerts on a weekly basis.

Value Proposition

Keeping total cost of ownership low and the performance of your SAP solution high is a tremendous value to your business – a value delivered by the SAP EarlyWatch Alert. Knowing the status of each SAP component in your solution allows you to:

  • Greatly minimize the risk of downtime
  • React to issues such as bottlenecks before they become critical
  • Know what is affecting the performance and stability of your solution

SAP EarlyWatch Alert aims to ensure smooth operation of individual SAP components by acting proactively, before severe technical problems occur. This monitoring tool is based on experience with thousands of installations giving you a tool to save time, reduce costs and keep your SAP solution running smoothly.

SAP EarlyWatch Alert is included in your maintenance agreement with SAP. Among the SAP systems for which the EarlyWatch Alert is available are all systems running on an NetWeaver ABAP or NetWeaver Java platform and certain BusinessObjects systems. For a complete overview of supported products see SAP Note 1257308 (FAQ: Using EarlyWatch Alert).

Prerequisites and Preparation of SAP EarlyWatch Alert Service in Focused Run

The following documentation link reflects on the prerequisites and preparation in the section "Preparing Focused Run Applications":

It describes prerequisites and preparation steps for the following SAP EarlyWatch Alert scenarios:

  • SAP EarlyWatch Alert (EWA) for ABAP
  • SAP EarlyWatch Alert (EWA) for Java
  • SAP EarlyWatch Alert (EWA) for BOBJ and Data Services
  • SAP EarlyWatch Alert (EWA) for HANA (only)

How to access SAP EarlyWatch Alert Service Report

The SAP EarlyWatch Alert Service is processed in FRUN but FRUN does not show any results of SAP EarlyWatch Alert Service. A Service result is published either in the One Support Launchpad as EWA Report or can be consumed online in SAP EarlyWatch Alert Workspace.

The SAP One Support Launchpad provide the Service Messages app/tile for customers to access and consume reports from SAP-delivered services. Details how to configure and use the app can be found in SAP KBA 2319793 (How to check service messages in SAP ONE Support Launchpad).

SAP EarlyWatch Alert - Processing Status

With Focused Run 2.0 FP 01 a new status overview reflects the processing status of SAP EarlyWatch Alert Service in FRUN. In Advanced System Management three new tiles are shown:

  • SAP EarlyWatch Alert Status
    Opens a new application to display the SAP EarlyWatch Alert processing status
  • SAP EarlyWatch Alert Reports
    Link to the viewer application in the SAP ONE Support Launchpad (S-user is required for log in)
  • SAP EarlyWatch Alert Workspace
    Link to workspace in SAP ONE Support Launchpad (S-user is required for log in)

The SAP EarlyWatch Alert Status application provides two capabilities:

  • The app displays the status of the SAP EarlyWatch Alert data processing on weekly basis. Transfer and communication statuses of the monitoring data between the managed systems, Focused Run, and SAP (where the reports are stored) are displayed.
  • You can activate or deactivate the SAP EarlyWatch Alert service on system level for non-productive systems - to decide for which systems reports shall be created.

Activation of SAP EarlyWatch Alert Data Processing

The list of systems in the application is pre-selected via the Scope Selection. By default, the SAP EarlyWatch Alert service processing is enabled for production systems to collect the corresponding data on weekly basis. With a switch to activate the service for a system the data processing can be turned on for systems were the service is currently inactive. This switch is meant to be used to activate the service for non-productive systems. The following scenarios are supported:

  • SAP EarlyWatch Alert for Application Server ABAP
  • SAP EarlyWatch Alert for Application Server Java
  • SAP EarlyWatch Alert for SAP Business Objects BI Platform (BOBJ) and SAP Data Services (DS)
  • SAP EarlyWatch Alert for SAP HANA (stand-a-lone)

With the switch to deactivate the SAP EarlyWatch Alert service for a system the data processing can be stopped for systems were the service is currently active. To quickly select active/inactive systems use the toggle switches above the system list:

SAP EarlyWatch Alert Processing Status Details

The SAP Early Watch Alert Status shows the data processing status for the current week and one week before. For all relevant activity its processing state (three status changes per week) is shown in the new UI. All three status indicators per week need to become green throughout a week for a successful processing. The overall rating is displayed in the correspondent row. Only with a green rating a user can expect that the report data is available for consumption in the cloud-based applications mentioned above.

The communication between the managed system, Focused Run, and SAP is taken place in three steps:

  • The Focused Run system requests service data for the SAP EarlyWatch Alert service, this request is picked up by the managed system.
  • The managed system answers the request and the service data is received by Focused Run system.
  • Focused Run transfers the data to SAP, where it can be consumed by cloud-based apps, e.g. the SAP EarlyWatch Alert Workspace.

To quickly distinguish a one-time from a permanent problem the transfer status is displayed for the last two weeks. If the current week show a red status the user can compare with the week before to see if an issue persists. With a click on the indicator icon a user can to see a little hint about the root cause (in case of red indicator) or when a step took place (in case of a green indicator).

SAP EarlyWatch Alert Workspace

For a convenient access to the SAP EarlyWatch Alert information, use the  SAP EarlyWatch Alert Workspace. This cloud service is available as a tile in the SAP ONE Support Launchpad. It is the central landing page which gives a comprehensive overview on your system landscape regarding stability, configuration, hardware utilization and performance. Drill-downs into KPI time series for a long-time range are provided, e.g. database growth, SAP HANA CPU and memory utilization and response times. A global search over all service alerts and recommendations offers a more efficient way to get a task list to improve the landscapes' health.

To use the workspace, you need an S-user with the Launchpad authorization Service Reports & Feedback on customer number level. The authorizations for the ONE Support Launchpad are provided by the Super Administrator on the customer side (see SAP KBA 1996168 and About the user, authorization and administrator concept). For Value Added Resellers, see also SAP KBA 2627899.

 

The SAP EarlyWatch Alert Workspace consists of several cards offering, among others, the following views:

  • With the SAP EarlyWatch Solution Finder you can perform a full text search over all your SAP EarlyWatch Alert reports for any search term or affected system. As a result, alerts (sorted by severity), recommendations by SAP and additional information is displayed. For every place of finding the affected systems are displayed; choose the system to see the complete corresponding paragraph of the SAP EarlyWatch Alert Report.
  • In SAP EarlyWatch Alert Reports, the rating for both the system and the underlying topics is displayed for every system, for which an SAP EarlyWatch Alert service had been executed. In a topic or subtopic, you can view detailed information including recommendations how to solve possible issues. And you can download the report as the well-known Microsoft Word document.
  • Based on the content of SAP the EarlyWatch Alert reports, use the SAP EarlyWatch Alert Dashboard to display the most important KPIs on system, database and application server level for one system. Drill-downs into KPI time series for a long-time range are provided, e.g. database growth, SAP HANA CPU and memory utilization and response times.
  • You can call the SAP EarlyWatch Alert Dashboard e.g. from the card Top 10 Systems, a bubble chart where systems are arranged by values characterizing the systems. In this chart an ERP system is usually situated in the upper half (high number of users), whereas BI systems are typically situated in the lower right quadrant (low number of users and large DB size).
  • The 2 Billion Record Limit of the SAP EarlyWatch Alert Service monitors and forecasts the number of entries in SAP HANA tables. These tables are restricted to two billion rows per partition (more precisely 2.147.483.648 - 2 to the power of 31), so in case a table is approaching this limit, you must take actions depending on the corresponding table. Use this app to get an overview which tables are approaching the limit including a prediction when the limit is reached, itemized into a mean, best-case and worst-case scenario. By default, the forecast is based on all previous measurements. You can, however, restrict the measurements used for the forecast.
  • The Top Deviation card displays the 10 systems with the largest response time deviation of the current week compared to the long-run average of the system; the displayed values are based on the most relevant task type of the respective systems. Use it to easily locate systems with exceptional performance issues.
     

All these functions are connected to each other, so you can easily switch between the different views e.g. during a drill-down. To keep the context during these switches, a global filter for customer, system and database type is available for all cross-system views. If you are responsible for one or several customer numbers and all the systems of these customer numbers, then it is best to use the customer number filter. If you are responsible only for specific systems from one or many customer numbers, use the filter dialog for System ID.