Nowadays the migration from on-prems applications to cloud is on high trend and of course you couldn't leave monitoring behind with the cloud based products.
So here is my first blog on SAP Cloud ALM Health Monitoring because SAP is more and more pointing to Cloud ALM as its own monitoring tool. As the Mainstream support for the Solution Manager will end in 2027, and Extended Support will end in 2030, sending a clear signal that it's time to transition to cloud-based monitoring solutions.
So the first question is what we can do and the features of Health monitoring in SAP CALM?
The answer is, In the Health Monitoring application you can check the health of your monitored cloud service and technical systems from an application and customer perspective. Technical metrics are collected on a regular basis and can be used to calculate the overall health of the monitored object. The monitored metrics are defined by the service itself and may differ for each service type.
Health Monitoring - Features
- Overview
In the overview screen you can see the current status of all cloud services or technical systems which are connected to Health Monitoring. An overall health is calculated based on the number of metrics in warning or critical status. - Monitoring
The metric details for each monitored object can be shown when it is selected from the overview page. There you can see a list of components and metrics. Each component or metric is represented by a tile which summarizes the current value and rating. By clicking on a tile you will get more details on all contained metrics. - Analytics
For each metric it is possible to show the historical values of the metric. Here you can identify trends or investigate at which time a specific resource shortage has occurred.
Before proceeding with the Health monitoring setup, there are prerequisites which needs to be fulfilled to enable the monitoring setup which are mentioned below. Kindly note based on the your product and ST-PI version prerequisites might change as well. The complete details is the blog is for ST-PI 7.40 SP26.
Prerequisites-
Before you can set up Health Monitoring in SAP Cloud Application Lifecycle Management, you have to connect your subscribed SAP cloud services to your SAP Cloud ALM instance.
This is done by setting up the Landscape Management Service. Please follow the Setting Up Landscape Management guide in SAP Help on how to perform the setup.
1-SAP_BASIS Release: 7.40 SP16 or higher
2SAP_UI Version: SAP_UI 740 SP15 or higher
3-Implement ST-PI 7.40 with latest released patches and keep them up to date to ensure the correct data collection. Also apply the collective correction from the below note. As my system in having ST-Pi 7.40 SP26 so I am applying this snote based on your ST-PI version you can apply the required corrections.
- 3421256 - Collective corrections as of ST-PI 7.40 SP26 for SAP Cloud ALM
4- Apply the DigiCert certificate in your backend systems under mentioned pse.
5- Now as the communication between your ABAP system and SAP Cloud ALM happens from the ABAP system towards SAP Cloud ALM.
To successfully establish the connection from the ABAP system to SAP Cloud ALM:
- You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system. You can get the service under the instances and subscription in SAP BTP--> SAP Cloud ALM instance now download the service key from the 3 dots icon on the right side.
- Reference SNote- 3111953
- You need to make sure that the following URLs can be reached:
- The Cloud ALM API URL (service key "endpoints":"Api" without /api)
- The Cloud ALM OAuth URL (service key "uaa":"url" extended by /oauth/token)
- In case you use a proxy in your network, please make sure that it is configured to allow calls to these URLs
- If your SAP ABAP system is hosted with SAP Enterprise Cloud Services (ECS), please open a service request with SAP ECS to add the following URLs to the "Allow-List" for your environment (Please note: This does not apply to SAP SuccessFactors Employee Central Payroll):
- Root URL: SAP Cloud ALM service key parameter "endpoints":"Api" without /api
- OAuth URL: SAP Cloud ALM service key parameter "uaa":"url
6-You will require two users in the managed ABAP system for the setup.
- To run transaction /SDF/ALM_SETUP, your personal user needs the PFCG role SAP_SDF_ALM_SETUP.
- Please note: In this role you need to maintain the authorization field S_BTCH_NAM > BTCUNAME either with '*' or with the user name of the user you plan to use as data collection background job user
- Second user to run the data collection background job: Please assign the roles as per below.
- SAP_SDF_ALM_METRIC_PUSH_CSA
- This role contains authorization objects delivered by SAP with no authorization. To use the SAP Cloud ALM scenario Configuration & Security Analysis (CSA), please maintain make sure the following authorization objects are maintained:
- S_RFC_ADM: ICF_VALUE = '*'
- S_DATASET: FILENAME = '*', PROGRAM = '*'
- S_LOG_COM: HOST = '*', OPSYSTEM = '*'
- SAP_SDF_ALM_METRIC_PUSH_CSA_S
- This role allows the detection of special users (such as SAP*) using default passwords
With the last step we are done with the preparation/prerequisite part of the health monitoring setup. With the next blog I will provide the setup steps.
