Real User Monitoring Administration (until Focused Run 1.00 SP02)

Open the Real User Monitoring Administration

Global Settings

On this tab you can check if the housekeeping job scheduled and when it has been executed the last time.

  • Enter the lifetime of the data: Number of days for single requests and number of days for aggregated data (available since FP01).
  • Enter the time when the housekeeping job should run.

Systems

In the systems area you can:

  • Add new technical systems
  • Deleted existing systems/configuration
  • Change thresholds
  • Navigate in case of trouble shooting to the relevant agents for the system.

Adding a Technical System

Click on Button Add System to open the LMDB search. 
Supported System Types are: ABAP, Java, HANADB (since FP01).

Search for a System, select it in the table below and click on OK.
Click on 'Apply and activate' to save your changes.

For a new added systems the credentials for the PUSH user (from SDA -> FRUN) needs to be provided. See also next step/tab.

Deleting a Technical System 

Select the system you want to delete and click the button Delete System.

Click on 'Apply and activate' to save your changes.

The configuration on the agent is deleted an data is no longer collected. Deleting a system does not delete the already collected data.

Changing Thresholds

If there are requests or applications where you expect a higher response time then the thresholds can be adapted.

The evaluation if a request execution is rated as green, yellow or red and if fast executions are aggregated are already done on the agent.

Each request type (like http, RFC,..) has a three default thresholds:

  1. Green→Yellow (ms)
    Executions below this threshold are rated as green.
  2. Yellow→Red (ms)
    Executions below this threshold are rated as yellow.Executions above this threshold are rated as red.
  3. Aggregation (ms)
    Executions below this threshold are aggregated already in the agent. This ensures that many fast requests do not blow the amount of data. 
    This threshold must be lower than the Green→Yellow threshold.

The flag Aggregate Errors decide if http calls which run into an error (e.g. status code 500) but are very fast are aggregated (if flag is set) or not.

Custom Thresholds

It is possible to create custom and system dependent thresholds by selecting the request type and clicking on button Add.


In the example above there are two additional thresholds for SAPGUI dialog requests. One for transaction SE80 and one for SE09. Both have different thresholds.

There are also two custom specific thresholds for https defined with wild cards. The first entry is for all https requests starting with /sap/bc/webdynpro/sap/Z which are aggregated if they are faster than 700ms and rated as red if they are slower than 4s. The second entry is for all https requests starting with /sap/bc/webdynpro/sap/Z and having TEST in the name which should be aggregated if they are faster than 600ms and rated as red if they are slower than 2s. Because this pattern is already matched by the first entry the second threshold will never taken into account.

For this reason you can change the order in the table by selecting entries and moving them up (button Move Up) or down (button  Move Down).

Note: When using wild cards for thresholds keep in mind that the first matching entry from top is taken into account.

By clicking on button Apply and Activate the changes are persisted and the configuration is send to the agent. Starting with collection the new thresholds are used to aggregate and rate the executions. 

Note: Historical values are not touched: changing thresholds do not change the rating of already collected data.

Push-User Credentials

The Agents need to know the the URL where they should push the data to and the credentials to login.

FP01
With FP01 this can be set in this step. It is possible to set or change the user or the password for several agents in one go. The password in the user master record (SU01) is not updated but only the value of the password is pushed to the agent.


Since FP02

With FP02 Real User Monitoring is integrated in Simple System Integration (SSI) setup. The credentials are sent by SSI to the agents. New password can be set with report RSSI_CHANGE_NETWORK_PASSWORD as mentioned in the master guide.

Request Description

It is possible to create for technical request name a more meaningful user friendly description which is then displayed in the monitoring. However configuration and filtering must be done for the technical names.