This is one stop global knowledge base where you can learn about all the products, solutions and support features.
The purpose of Real User Monitoring is to provide transparency about the usage (executions) and the performance (response times) of user interactions . It supports the monitoring request executions from different platforms with a unified user experience using a common look-and-feel and handling pattern.
The basic concept is to get all user interactions and the relevant server requests which are the correlated in the Real User Monitoring application. Request executions are rated not based on fixed thresholds but on historical values.
Real User Monitoring shall help IT users and Business users to understand how often applications are executed and what is the response times for the end-users.
Real User Monitoring in Cloud ALM collects front-end measurements and display these as following types:
Real User Monitoring in Cloud ALM collects back-end measurements and display these as following types:
Overview of the performance metric for services in your scope and your favorites in the selected time range is displayed as the Apdex (Application Performance Index).
This is an open standard developed for measuring the performance of applications. For more information, see https://en.wikipedia.org/wiki/Apdex.
The page consists of two sections, for more information, see the in-app help of the sections:
In the Overview the development of the Apdex over time for the services in scope is displayed.
In the Favorites the Apdex for your favorites is displayed.
The rating is done based on historical values.
By clicking on a request type you navigate to the Request Overview with filtered settings.
Request Overview
The
Request Overview
provides for the selected time range.
By choosing the icon in the last column you drilldown and see further details which (user) actions have been executed.
By choosing the icon in the last column you drilldown and see further details at which timestamps the actions have been executed.
Analysis View
Analysis View provides flexible selection of metrics and dimensions for analysis and download functionality
Available metrics:
Dimensions:
Frontend Overview
In this page, the most important front-end usage and performance metrics for the following frond-end request types are displayed:
For more details on prerequisites, setup, housekeeping, and customer support, please check the Real User Monitoring - Setup & Configuration page.
To help troubleshoot issues, check the Real User Monitoring Troubleshooting page.
This page contains some hints for troubleshooting when for example some pages or views are empty.
As starting point you should classify the problem:
Is the configuration for managed system executed?
Is the communication arrangement for scenario SAP_COM_0527 created and :
Are the scheduled jobs running?
Problems during setup, data collection or push are logged in application log.
Wrong time zone settings might be the reason for missing data.
Execute report
RSDBTIME
or
TZCUSTHELP
. If they report an issue like
ERROR: ABAP system timezone setting inconsistent!
ABAP system timezone (DB table TTZCU) is: CET
This is inconsistent with date and time of ABAP-Processor and database!
or
System time zone or UTC timer is incorrect.
Correct the time zone settings for that system(client).
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.
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.
* To setup Real User Monitoring please follow the monitoring setup guide and make sure 'Collect Performance' is flagged.
For services and systems that use PULL data collection, you will have to activate the monitoring data collection, after creating the endpoint in Landscape Management.
Currently the following services or systems use PULL data collection:
To activate the data collection proceed as following:
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:
After the configured days for aggregated executions data is deleted.
Be aware that SAP provides you in fair usage concept 8 GB HANA memory per month. If you extend the given memory you might need to subscribe additional memory blocks with our BTP service SAP Cloud ALM memory extension.
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 an 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).
In case you encounter problems using or setting up Real User Monitoring in SAP Cloud ALM, please report an incident using one of the following components:
Please select your SAP Cloud ALM tenant when reporting the incident.
In this video, you will learn the first steps of Real User Monitoring, including:
In this video, you will get to know the analysis page and learn how to:
In this video, you will get to know the front-end view of real user monitoring and learn how to:
Real User Monitoring in Cloud ALM collects data for these request types:
| Product | Request Type | Description |
|---|---|---|
|
SAPUI5 | Frontend Measurements of Fiori and SAPUI5 components |
|
WebDynpro | Frontend Measurements of ABAP WebDynpro |
|
WebGui |
Frontend Measurements of
SAP
GUI for HTML
|
|
HTTPS | Backend Measurements of https requests |
|
Dialog | Backend Measurements of SAPGUI requests |
|
WS | Backend Measurements of Web Service requests |
|
SAPUI5 | Frontend Measurements of Fiori and SAPUI5 components |
|
WebDynpro | Frontend Measurements of ABAP WebDynpro |
|
WebGui |
Frontend Measurements of
SAP
GUI for HTML
|
|
HTTPS | Backend Measurements of https requests |