Real User Monitoring - User Interface


Real User Monitoring uses, like the other applications in SAP Focused Run, the shell which contains:

  • The Side Navigation on the left side
  • The Header on top
  • The Pane Bar on the right side
  • One page in the middle

Each page can contain multiple views.

Side Navigation 

The Side Navigation contains default pages and custom specific pages. Default pages cannot be changed or deleted but they can be set to hidden.

RUM has per default these pages:

  • Overview
  • Requests
  • Cards
  • End-User
  • Hot Requests (since SAP Focused Run 2.0 FP01)
  • Hot Requests (Location) (since SAP Focused Run 2.0 FP02)
  • 24 Hour Status Profile (since SAP Focused Run 2.0 FP01)
  • Topology (since SAP Focused Run 2.0 FP01)
  • Topology Requests (since SAP Focused Run 2.0 FP03)
  • Client Overview (since SAP Focused Run 2.0 FP03)
  • Execution Flow (since SAP Focused Run 3.0)
  • Click Path (since SAP Focused Run 3.0 FP01)
  • HTTP Statistics (since SAP Focused Run 3.0 FP01)


The header contains the scope selection, time frame selection, data quality, refresh timer and notification button.

Scope Selection

Here you can define for which configured systems Real User Monitoring data is displayed.

For SAP Focused Run 2.0 SP00 only System Type ABAP and Java are supported, with SAP Focused Run 2.0 FP01 additionally HANA DB. Enter a list of system IDs or the or selection fields to define the query.

Default Pages

Default pages cannot be changed or deleted but they can be set to hidden. However for some pages like the Overview or the Request page, it is not recommended to hide them because otherwise the navigation to the requests cannot be displayed.


The Overview page contains the following three views 

Status Overview

In the status overview you can see the number systems in scope and for each available and monitored request type how many percent of the them are running longer as expected. The numbers are the percentage value of executions above the red threshold. 

The background color of the boxes can be changed globally (see above). 

System Overview

In the System Overview you can see the different ratings per system and request type and can identify how many requests of a particular request type are executed and which system handles the highest number of requests.

In case one request type or system is very dominant like in the screen shot above the values can be also display a percentage values:

The percentage values are calculated per system and request type. They cannot be compared with the values from the Status Overview.

Alert Ticker 

In the alert ticker you can see all alerts that have been raised recently for the systems in scope. These alerts are coming from System Monitoring. 


The view Request Overview is used very often as jump-in from other views. It allows a detailed drill-down into each single execution as long the execution is above the configured threshold for aggregation.


When reaching the request view from any other view the Filter is usually set. The filter icon is activated and you can see in the information bar which filter values are set:

Nevertheless you can change the filter at any time. The possible filter values depend on the depth of the drill-down.

In the entrance view it is possible to filter for:

  • Time Frame (either inherited from global selection or different time frame)
  • Request Type (RFC, SAPUI5, https(s), WS, Dialog)
  • Request Name
  • User Name
  • System
  • Location Filter (If location attributes are used)
  • User Type (Either synthetic users or only real users or both types)
  • Maximum number of hits (default = 100)

All filter values are case sensitive.

Default View

When the view is called without any filter for example from standard page Request Overview no filter is set at all and you can see the top 100 requests executed in the selected time frame for all systems in the scope. By default the result is sorted by the number of Red Executions.

The request name is dependent of the request type

  • RFC
    For RFC requests the name is the function module name.

  • http(s)
    For http(s) requests the name is the URL path.

  • WS
    For web service requests the name is the web service name .

  • Dialog
    For SAPGUI dialog steps the name is the transaction code.

  • SAPUI5
    For SAPUI5 requests the name is the SAPUI5 component or the Fiori application.
  • Web Dynpro
    For ABAP Web Dynpro the name is the WD application name.
  • Web GUI
    For ITS Web GUI the name is the transaction code.

When clicking on the button with the glasses you can switch between Default, Performance and Usage view.

Perfomance View 

In the Performance view the result is sorted by the percentage of red executions.

Usage View

In the Usage view the result is sorted by the number of total executions. Here you can also see by how many different users a request or application is executed in the time frame,


By clicking on an entry in the list you can drill down further. 


When clicking on a request name you reach the action. This is dependent of the request type.  

  • RFC
    For RFC requests the action is the function group name.
  • http(s)
    For http(s) requests the action is the http method like GET or POST.
    For OData requests the action contains additionally the entity set, the function name or the batch operation
  • WS
    For web service requests the action is the web service operation or method.
  • Dialog
    For SAPGUI dialog steps the action is the dynpro/screen number and the function code like 0100-SAVE
  • SAPUI5
    For SAPUI5 requests the action is the UI element and the triggered action like button3_click
  • Web Dynpro
    For ABAP Web Dynpro the action is the UI element and the triggered action like WD02BA-Button-Press
  • Web GUI
  • For ITS Web GUI the action is the UI element and the triggered action like M0:37::btn[47]_Press


Clicking on an action leads to the last 100 executions of the selected time range.

The column Net Time(%) indicates how many of the request response time is spent in the component mentioned in column System. A low value means the time is spent somewhere else and need to be investigated further by drilling down deeper.

If you are only interested in red and yellow executions the green executions can be filtered out.

Instead displaying the values only as a table it also possible to display the executions either as line chart or as a 24h profile.

24h Profile

If the selected time frame is less than 24 hours the query is expanded to the last 24h.The executions of the selected request name are displayed as distribution over the 24 hours of a day.

The action name is not taken into account for the 24h profile.  

Execution Details

In the deepest drill down level you can see which other requests in which other components are triggered by this request. It can be very simple:

Or more complex:

If the tree is too complex you can zoom in scroll in the tree or switch to the table mode.

The percentage in the right upper corner is the percentage of this request compared to the overall response time of the first/root node of this tree.

By double click on a box you get more details about the request in that component for example:

Response Time: Elapsed time or gross time for that request in that component
Net Time: Net time spent in that component = Gross time minus time for outgoing requests
Wait Time: Time in the component for example to get a resource (Lock, work process,..)
Memory: Consumption of this request in this component
Net Time Percentage: Percentage of the net time spent in the component compared to the response time of the root node of the graph
Transaction ID: SAP Passport field; Identifier of request
Connection ID: SAP Passport field;Identifier of a connection between two components
Connection Counter: SAP Passport field; Counter of used connection
Pre Component ID:  SAP Passport field; Previous Component ID


Check for Expensive Statements

Starting with FRUN 3.0 it is possible to check for expensive statements for a backend request if the system is running on SAP HANA and if the request has a high DB time.
The expensive statements from HANA DB need to be enabled in the HANA database first. See also or FAQ note 2180165 (FAQ: SAP HANA Expensive Statements Trace)

It requires the Statement HANA_SQL_ExpensiveStatements_RUM in the SAP Hostagent which is available with SHA PL50.

See also note 2555664 - Enable HANA Dashboards and AdHoc SQLs in System Analytics for Focused Run


The page cards displays by default 5 cards. For each possible request type (RFC, SAPUI5,..) one card. In the filter the selection criteria can be changed temporarily but as for other default pages they cannot be persisted.

By clicking on a card you reach the Request Overview with the filter criteria of the selected card. To create your own card view check page RUM Card View.


The End-User view shows which operating system (including version) and which browser (including version) has been used by end users to trigger requests in the selected systems.

These information is extracted from SAPUI5 requests and therefore not available for other request types. It is also possible to combine the information in a single diagram. The filter settings can be used to specify the displayed information by:

  • Timeframe
  • Request Name
  • User Name
  • System
Since FRUN 2.0 FP03 it is possible to jump to page Client Overview to see which user is using the mentioned OS or browser version.

Hot Requests

On the page Hot Requests you can see a tree map of requests of one system grouped by the request type. There are three different variants available (Performance, Workload and Usage).

Performance View

In the Performance view the sizes of the boxes are defined by the number of red executions. The more red executions the bigger the size of the box. The color of the box is rated based on the percentage of red executions.

Starting with FRUN FP02 it is possible to hide boxes if they are too huge and hide other requests:

Workload View

In the Workload view the the sizes of the boxes are defined by the total response time of each request. The color of the box is rated based on the percentage of red executions.

Usage View

In the Usage view the sizes of the boxes are defined by the number of unique users affected by a request name.

24 Hour Status Profile

In the 24h status profile you can see for a long time frame how the behavior of the requests are distributed on the 24 hours of the days. The color of the box is rated based on the percentage of red executions.



The Topology view gives you an overview about the traffic between the systems. The thicker the line the more requests are executed between the systems. The color indicates if the average response time is above or below the thresholds defined for this request type. Filters can be set to display only the incoming or the outgoing request for the systems and for the request types.

Topology Request

The Topology Request view gives you an overview about the traffic between the systems as a table. In addition to the Topology view it provides the request name. From here it is then possible to jump to page Request Overview for drill down analysis.

Client Overview

The page Client Overview gives you an overview about the user operating system and browser versions the users have used in the selected time frame. It is possible to filter for users with wild cards e.g. C*, D* to display all users starting with C or D.

Execution Flow (Since FRUN 3.0)

The page Execution Flow gives you the sequence which activities an end-user has executed in the client and shows the correlated backend requests. This page is only visible for users having authorization to display sensitive data e.g. having role SAP_FRN_APP_RUM_ALL. You either need to enter the user id or the RootContextId in the filter.

Requirement to have end-user activities is SAP_UI 7.53 in managed system for ABAP WD or HTML GUI.

Click Path (Since FRUN 3.0 FP01)

The page Click Path shows two views:

Session KPIs

This view contains for each system and front-end request type:

  • Total visits
    Number of sessions or navigation steps with same RootCtxId
  • Visits
    Number of visits with more than 1 click
  • Unique Apps
    Number of applications or components that are called
  • Clicks
    Total number of clicks
  • Avg. Session Time
    Average length of the visits from first to last click in ms
  • Max. Session Time
    The maximum length of a visit between first and last click of a visit (in ms)
  • Median Session Time
    Median value of the length of all visits.

Click Path

Click path displays the sequence which activities all end-users have executed in the client and shows how often navigation steps from one to another component has been executed. If a navigation step is within an application or component it is displayed as number of self references within the box. 

The click path works only for Fiori applications or SAPUI components. For ABAP WD or HTML GUI each application is counted as a separate visit.


HTTP Statistics (Since FRUN 3.0 FP01)

The page HTTP Statistics shows 4 views:

HTTP Status Codes

This view contains for the selected system the number of status codes for incoming http requests.

Top 10 Average Response Time

The 10 incoming http requests for the selected system with a successful http status code (2*).

HTTP Server Errors per user

Incoming http requests for the selected system with a server error (http status code 5*) per user.

HTTP Client Errors per user

Incoming http requests for the selected system with a client error (http status code 4*) per user.

Custom pages can be created for incoming http requests (Capability RUM HTTP Metrics) or outgoing http requests (Capability RUM HTTP Outgoing Metrics) based on the Generic View.

Custom Pages

For the default pages described above it is not possible to persist changed filter values. To allow this a user can create his own pages and add the views he prefer or need for his task.

A customer page can be create either by clicking on the plus sign in the side navigation (on the left) or by opening the personalization and clicking on button 'Add custom page'.

Page Management

Here you can define if a page is either public and visible to all other users or private and only visible for your user. You should give the page a meaningful name and if you want you can change the icon for this page. From here the page can also be hidden then it does not appear in the side navigation.

View Management

When multiple views should be displayed on the page you can define a grid layout.

The available views can be copied via drag and drop to the position on the page.

Each view have some filters that can be persisted.

A more detailed description of the the Generic View can be found here.