Cloud EWA information

[Former Member]

Hi folks - we have a SM 7.1 sp#7 system hooked up to huge # of managed systems and one of the things we use SM for is the EWA reporting. In working on some issues w/ that recently, I came across this link on the SAP portal

https://launchpad.support.sap.com/#/ewaworkspace

I read here that the SAP recommendation is to start using the EWA's here in this "cloud EWA" portal. As opposed to ones sent from our SM systems via email.

"You can read the reports from your SAP Solution Manager or email them to assigned recipients. However, SAP recommends to use the cloud-based SAP EarlyWatch Alert Workspace, the central landing page for a comprehensive overview on your system landscape regarding stability, configuration, hardware utilization and performance. Here you can read the reports in a new format containing all details on alerts and recommendations, drill-downs into KPI time series, and forecasts for possible future issues. It offers comprehensive function for personalization and global search. If you use the Focused Run for SAP Solution Manager solution, reports for Java and SAP BusinessObjects systems can also be found in the SAP EarlyWatch Alert Workspace app."

QUESTION: So I see the ewaworkspace has all the fancy graphical UI but still let's you drill down and find and download the full EWA report. But what's the difference (if any) between these and what's available on the SM system? If they are different - then how are they technically generated?

Thanks

[SusanneGlaenzer]

Hi Ben,

1. The main difference is that EWA Workspace provides predictive alerts, that are only calculate at SAP. The predictive use cases are:

- SAP HANA 2 Billion Limit Forecast (https://blogs.sap.com/2018/10/29/the-new-2-billion-record-limit-in-the-sap-earlywatch-alert-workspac... )

- SAP HANA Indexserver Memory Forecast (https://blogs.sap.com/2019/10/01/memory-forecast-for-sap-hana-with-sap-earlywatch-alert-workspace/ )

- SAP HANA Data Footprint Forecast

- Critical ABAP Number Ranges ( in development )

2. Data can be send from managed system or from SolMan, FRun or HANA Cockpit.

Best regards

Susanne

[Former Member]

Thanks Susanne

Our SM system has not been kept up very well - we have a few hundred managed systems connected but only a dozen or so that seem to regular produce an EWA report. Most do not. We have just a small# of systems (2), not receiving the EWA regularly now, which are critical to get fixed as far as the EWA. In researching that issue I have found numerous issues:

---SM version is 7.1 sp#7 - so it's out of support since 12/31/17

---ST* plugins on SM and most managed systems are several years old

---SM system itself, and the most managed systems have not been "fixed" as far as the Jan'20 changes SAP made to their backbone connectivity

---many jobs that run on SM side, run extremely long (e.g. SM:EXEC SERVICES, CCMS_ASR_AGGR_DATA_UPDATE, E2E BI HOUSEKEEPING) and fixing that w/o patching/upgrading SM is not proving easy (SM system hasn't been kept up well and I suspect that it probably has grown into too much data.... and has slowed down over the past few years to where it's become a real problem)

Question - given all that, & if your goal were just to get the EWA report to regular generate for those 2 critical (abap only) systems (and that we really don't care about all those new predictive analytic features and capabilities ---- all we need is the old style report), would you concentrate on setting them up to generate in ewaworkspace (i.e. bypass SM and connected managed system directly to ewaworkspace)? Or would you focus on getting them to generate correctly/regularly from the 7.1 SM? I'm assuming you have a better feel for which of those would be easier to do and that's what I'd like to know.

Thanks

[Former Member]

And is the content of the ewaworkspace reports pulled from SM or directly from each Managed System?

Thanks