Prerequisites

Before you can set up Real User Monitoring in SAP Cloud ALM, 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.

Setup

Connect Managed Services / Systems

Please follow the documentation below on how to connect the managed services and systems to SAP Cloud ALM.

After connecting the managed services and systems, you have to activate the Real User Monitoring data collection for the managed services or systems that use PULL data collection. This is described in the next section.

For the following services you only need to activate the data collection (see below):

  • SAP Ariba Category Management
  • SAP Batch Release Hub for Life Sciences
  • SAP Broker Reconciliation for Commodity Derivatives
  • SAP Cell and Gene Therapy Orchestration
  • SAP Order and Delivery Scheduling
  • Integration Hub for Life Sciences
  • SAP Variant Configuration and Pricing
  • SAP Digital Vehicle Hub
  • SAP Business Network Material Traceability
  • SAP Intelligent Clinical Supply Management
  • SAP Task Center
  • SAP Predictive Replenishment
  • SAP Intelligent Agriculture
  • SAP Digital Currency Hub
  • SAP Business Network Supply Chain Collaboration, clinical trials add-on 

* To setup Real User Monitoring please follow the monitoring setup guide and make sure 'Collect Performance' is flagged.


Activate Real User Monitoring Data Collection

To activate the data collection proceed as following:

  1. Open the "Real User Monitoring" application from the launchpad
  2. Add the relevant cloud service or system to the scope
    1. Open the scope selection
    2. Search for your service or system
    3. Mark the checkbox in front of the service or systems
    4. Click "Apply"
  3. Open the configuration panel, by clicking on the rack-wheel icon in the upper right corner
  4. Open the "Systems" panel and activate the data collection for your service or system by switching the slider from "OFF" to "ON"
Remove Real User Monitoring Configuration

To remove the Real User Monitoring configuration proceed as follows:

  1. Open the "Real User Monitoring" application from the launchpad
  2. Add the relevant cloud service or system to the scope
  3. Open the configuration panel, by clicking on the rack-wheel icon in the upper right corner
  4. Open the "Systems" panel and activate the data collection for your service or system by switching the slider from "ON" to "OFF"

Housekeeping

Under Configuration it is possible to specify the retention time in days for single executions (maximum 14 days) and aggregated executions (maximum 370 days).

After the configured days for single executions data is aggregated per hour for that dimensions:

  • Service
  • UI Application/Request Name
  • User Action
  • User Name

After the configured days for aggregated executions data is deleted.

FAQ's

There is no direct impact on the end-users.

For ABAP based systems a job is scheduled collecting every few minutes (depending on the entered collection period) for each use case the data. These collections are started via aRFC if enough work processes (WP) are free. The runtime depends on the amount of data to be collected. 

The user names are hashed in case that the user doesn´t have the role to access the sensitive data; Only the user has the role of Real User Analyst Sensitive or Real User Analyst Administrator is able to see the real user names.

The user actions are dependent of the application. Therefore all user actions are displayed per application. 
In the Analysis View you can create your own query to display for example all executed applications and actions.

The percentage in the upper right corner is the percentage spent net in that component. Some requests are executed in parallel and some time is spent on network (between the boxes).

The front-end response times are usually measured by the framework in the browser (SAPUI5, Web Dynpro, Web GUI) or provided by the application (e.g. SAP Analytics cloud, Cloud for customers).
The back-end response times are measured in the back-end. For ABAP based systems data is extracted from the statistic records. 

Requests of type SAPUI5/Frontend have some measured values that are different from other request types.

These are:

  • Round Trip Time (start time of first server record until end time of the last server record per round trip)
  • Network Time
  • Number of Round Trips (number of server requests initiated by this user interaction)

Response time is the elapsed end-user time measured in the browser.

Net Time is the time spend by the application in the browser. It is approximately the difference between the Response Time and the Round Trip Time influenced by the accuracy of the measurement. See also in the picture below.

The operating system and the version as well as the browser and its version is detected by frameworks (SAPUI5 or WD UR) in the managed system. Sometimes the platform detection changed and then a probably an old OS version (WIN_3) or a not yet available version (WIN_13, WIN_15) is displayed. It needs to be ensured that a recent Unified Rendering (UR) version is used, see also SAP Note 3449601(opens in new tab).

It is not possible to change the action names in the RUM UI. But for custom developed SAPUI5 applications the developer can map technical names to human readable names using the FESRHelper:

Coding snippet example:

import FESRHelper from "sap/ui/performance/trace/FESRHelper";

import Element from "sap/ui/core/Element";

// …

const kpiTag = Element.getElementById("sap.fe.cap.travel_analytics::BookingsList--kpiTag-fe::KPI::KPI1::_akt::_kpi");

FESRHelper.setSemanticStepname(kpiTag, "press", "KPI Tag"); // max. 20 characters

Customer Support

In case you encounter problems using or setting up Real User Monitoring in SAP Cloud ALM, please create a case(opens in new tab) using one of the following components:

  • SV-CLM-OP-RUM – Real User Monitoring UI
  • SV-CLM-OP-PM – Performance Monitoring Service

Please select your SAP Cloud ALM tenant when reporting the case.