- SAP Managed Tags:
Real User Monitoring is one application out of SAP Cloud ALM for Operations.
Real User Monitoring (RUM) is a monitoring application/technology that analyses end-user's experience for on-premise or cloud-based application.
It provides permanent measurement of all real user requests in a system landscape covering performance as well as utilisation aspects.
RUM differs from Synthetic User Monitoring (SUM) in that it relies on actual user clicking on the page to take measurements rather than recorded script tests playing a given set of test steps.
RUM and SUM are the perfect combination to understand users behaviour and monitor proactively on-premise or cloud-based application
The basic concept is to correlate all user interactions with relevant server requests in the Real User Monitoring application.
The request executions are rated dynamically on historical values and not on fixed thresholds.
The purpose of Real User Monitoring is to provide transparency into the usage (executions) and the performance (response times) of user interactions. RUM helps IT users and business users understand applications executions and response times for end-users.
Before you can configure Real User Monitoring in SAP Cloud ALM, you must connect your subscribed SAP cloud services or your on-premise system to your SAP Cloud ALM instance. Please follow the Setting Up Landscape Management guide in SAP Help on how to perform the setup.
The summary view provides all user interactions sorted by requests types (SAPUI5, RFC, Dialog) displayed with the Apdex (Application Performance Index).
The requests detail view provides the number of total executions, average response time and number of distinct users for each selected requests.
The response time and net execution time of single request execution can be accessed in the following view:
Frontend usage and performance metrics for the frond-end request types can be analysed in the following view:
Thanks for reading.
Real User Monitoring (RUM) is a monitoring application/technology that analyses end-user's experience for on-premise or cloud-based application.
It provides permanent measurement of all real user requests in a system landscape covering performance as well as utilisation aspects.
RUM differs from Synthetic User Monitoring (SUM) in that it relies on actual user clicking on the page to take measurements rather than recorded script tests playing a given set of test steps.
RUM and SUM are the perfect combination to understand users behaviour and monitor proactively on-premise or cloud-based application
Concepts
The basic concept is to correlate all user interactions with relevant server requests in the Real User Monitoring application.
The request executions are rated dynamically on historical values and not on fixed thresholds.
Benefits
Problem Solving
RUM helps you by detecting anomalies in real time and troubleshooting these problems to improve the digital experience of your end users.
Transparency
The purpose of Real User Monitoring is to provide transparency into the usage (executions) and the performance (response times) of user interactions. RUM helps IT users and business users understand applications executions and response times for end-users.
Segmentation
RUM provides you with the possibility to analyse your users' experience with different attributes as browsers types, connection types, application, location, operating systems.
Pre-requisites
Before you can configure Real User Monitoring in SAP Cloud ALM, you must connect your subscribed SAP cloud services or your on-premise system to your SAP Cloud ALM instance. Please follow the Setting Up Landscape Management guide in SAP Help on how to perform the setup.
Summary View
The summary view provides all user interactions sorted by requests types (SAPUI5, RFC, Dialog) displayed with the Apdex (Application Performance Index).
Requests Detail View
The requests detail view provides the number of total executions, average response time and number of distinct users for each selected requests.
The response time and net execution time of single request execution can be accessed in the following view:
Frontend View
Frontend usage and performance metrics for the frond-end request types can be analysed in the following view:
Thanks for reading.
