Technology Blog Posts by Members
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Health Monitoring in SAP Cloud ALM – Beginners Guide

NiharikaSol
Explorer
3 weeks ago
0 Kudos
1,288

Structure of this blog

This blog is structured to understand the following:

  • Health Monitoring Overview
  • Setup of health Monitoring
  • KPI Threshold Mapping
  • Creating Events in Health Monitoring
  • Alerts Handling in Health Monitoring
  • Conclusion

Health Monitoring Overview

Health Monitoring is a functionality in SAP Cloud ALM that provides an overview on the healthiness of all cloud services and on-premise systems connected to the Cloud ALM.

 We can check it from an application and customers perspective. The idea of Health Monitoring is to provide a central view of all our services in our landscape and to have a central alerting capability.

NiharikaSol_0-1750248922501.png

 

Application works by constantly connecting metrics about health status of cloud services of systems, metrics regarding to the usage, usage of resources and these metrics that are regularly collected are sent to SAP Cloud ALM into Health Monitoring Application which displays the data we can use to monitor, do analytics, and configure alerting using thresholds.

In the Health Monitoring app we can check the health of monitored cloud services and technical systems from an application and customer perspective.

NiharikaSol_1-1750248922509.png

The metrics are collected on a regular basis and can be used to calculate the overall health of a managed component.                           

In detail, the following features are available:

  • In the home page of the app, we can see the current status of all cloud services or technical systems which are connected to the Health Monitoring app, grouped by the different service types. An overall health is calculated based on the number of metrics in warning or critical status.

NiharikaSol_2-1750248922516.png

 

  • The metric details for each monitored service or system are displayed when we select it from the home page. Each component or metric is represented by a tile which summarizes the current value and rating. By clicking a tile, we will get more details on all contained metrics.

NiharikaSol_3-1750248922526.png

  • For each metric you can display the historical values of the metric. Here you can identify trends or investigate at which time a specific resource shortage has occurred. This will provide metrics for:
  • The ABAP system (for example, work process utilization, short dumps, heap memory, ICM and gateway resources).
  • The HANA database (for example, service status and memory utilization).
  • Hosts (such as CPU, memory and disk utilization).

NiharikaSol_4-1750248922551.png

Setup of health Monitoring

  • Connect service or system to SAP Cloud ALM instance in Landscape Management. Then we can set up the Health Monitoring itself.
  • The monitoring is activated automatically after we have subscribed to SAP Cloud ALM Service.

Add a system/service to be monitored.

NiharikaSol_5-1750248922553.png

 

Give the required details:

NiharikaSol_6-1750248922561.png

 

Configure the supported use case by switching the toggle ON.

NiharikaSol_7-1750248922578.png

 

KPI Threshold Mapping

We can either use the “Default SAP threshold” or can modify to a new threshold after customer landscape study to make the monitoring as optimized as possible.

NiharikaSol_8-1750248922588.png

 

Creating Events in Health Monitoring

We can also create events and map the below criteria for monitoring optimization.

NiharikaSol_9-1750248922611.png

 

  • Create Alert

Switch the toggle ON to enable Alerting

NiharikaSol_10-1750248922614.png

 

  • Send Email to
  • Switch the toggle ON to enable Alerting
  • Add the recipients by clicking on “+” sign,

NiharikaSol_11-1750248922623.png

 

 

  • It will populate the verified recipients, maintained in the Notification Management tile under Operations.

NiharikaSol_12-1750248922635.png

 

  • Send Operation Flow
  •  Switch the toggle ON to enable Operation Flow
  • Add the Operation flow by clicking on “+” sign,

NiharikaSol_13-1750248922641.png

  • It will populate the Operation Flows, maintained in the Operation Automation tile under Operations.

NiharikaSol_14-1750248922661.png

What is Operations Automation?

With Operations Automation, we can automate procedures related to the operation of the system landscape. These procedures are called Operation Flows in the context of SAP Cloud ALM for Operations.

These Operation Flows could be one of the following procedures:

  • Standard operational procedures related to the operations of your SAP Solution Landscape.
  • Problem resolution procedures triggered by alert and event processing.

Operations Automation in SAP Cloud ALM offers several benefits:

  • It enables faster resolution of detected problems by providing automated operation flows. This ensures that issues are addressed efficiently.
  • The operation flows generate an audit trail which allows for easy tracking and analysis.

                  Register Operation Flow:

                  We can register new operation flows of type:

NiharikaSol_15-1750248922669.png

 

To register a new operation flow definition, enter the following data:

  • Endpoint: The endpoint is already filled based on the selected automation engine type. If multiple endpoints exist for one automation engine type, you can enter any endpoints from the value help.
  • ID: Select the process and workflow, intelligent RPA automation, or automation pilot command that should be triggered from SAP Cloud ALM from the value help.
  • Use Case: Select the relevant use cases that are to be assigned to the operation flow.
  • Input Reference: This is an optional parameter, which is applicable only for the Automation Pilot commands. If not, all the required input parameters for the command are filled by SAP Cloud ALM. Enter an input reference in Automation Pilot that fills the missing input parameters. Select the input reference during command registration in SAP Cloud ALM.

Once we have decided on external Operations Automation engine, we need to setup an end point in the Landscape Management, before we can start an automated or manual execution of an operation flow.

To create an endpoint in the Landscape Management app, Click on “Add” under the selected Service:

NiharikaSol_16-1750248922693.png

 

Prerequisites for the Operation Flow setup in SAP Cloud ALM are:

  • We have subscribed to SAP Automation Pilot or SAP Build Process Automation or both.
  • The SAP Automation Pilot and SAP Build Process Automation tenant are listed in Landscape Management as cloud services.
  • An endpoint point is created in Landscape Management to SAP Automation Pilot and/or SAP Build Process Automation.

Automated execution of operation flows:

  1. A monitoring use case detects a problem and sends a monitoring event to Intelligent Event Processing.
  2. Intelligent Event Processing triggers the assigned operation flow in SAP Build Process Automation or SAP Automation Pilot.
  3. The operation flow executes the relevant problem resolution steps.
  4. The triggered operation flow and its status are visible in alert details (if alert was triggered).

Manual execution of operation flows:

  1. A monitoring use case detects a problem and sends a monitoring event to Intelligent Event Processing.
  2. Intelligent Event Processing creates an alert and sends an email notification.
  3. The alert processor analyses the alert in the alert inbox, searches for a suitable operation flow and starts it.
  4. The operation flow executes the relevant problem resolution steps.
  5. The triggered operation flow and its status are visible in alert details.
  6. Alert processor confirms alert.
  • Send Chat Notification
  • Switch the toggle ON to enable Chat Subscriptions
  • Add the Chat Subscriptions by clicking on “+” sign,

NiharikaSol_17-1750248922697.png

  • It will populate the Chat Subscriptions, maintained in the External API Management

tile under Administration.

NiharikaSol_18-1750248922713.png

Refer  : Integration with an external chat system: https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/intelligent-event-processing/i...

  • Create Ticket
  • Switch the toggle ON to enable Incident creation
  • Add the Ticket Subscriptions by clicking on “+” sign,

NiharikaSol_20-1750248922716.png

  • It will populate the Ticket Subscriptions maintained in the External API Management tile under Administration.

Refer : Integration with an external ticket system: https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/intelligent-event-processing/i...

 

  • Store Event Payload for 24 Hours
  • Switch the toggle ON to enable Store Event Payload for 24 Hours

NiharikaSol_22-1750248922720.png

When this option is enabled, the event payload is stored in the Intelligent Event Processing data store for 24 hours. We can then access the data store and consume the event payloads using the Raw Data Outbound Logs API for Intelligent Event Processing. 

Alerts Handling in Health Monitoring

The alerts are raised once the threshold has been met, Please note that consecutive Yellow or Red statuses will not trigger additional notifications.

Note: As of now, Cloud ALM does not send a new Alert/Event if it is resolved (from Red/Yellow to Green). 

We can filter the alerts by below criteria in Alert Management app of Cloud ALM under Health Monitoring.

NiharikaSol_23-1750248922736.png

Conclusion:

Health Monitoring application offers us the following features:

  • We can monitor the availability of services, systems, and components.
  • We can monitor the trends in the resource usage. For example, how many users are logged on or resources used by the service.
  • We can see information about certificates with their expiration date.
  • It will provide us with system monitoring capability in SAP Cloud ALM showing us for example issues on a database level or information about CPU memory usage.
  • We can check the reported errors and configure alerting.

Thank you for reading the blog!

 

 

 

 

 

 

1 Comment