Synthetic User Monitoring

Synthetic User Monitoring (SUM) enables you to monitor the performance and availability of a production system from a client-side perspective.

The monitoring is based on scenarios, also referred to as scripts, that are executed on different locations, also called robots. The system measures the performance by measuring the scenario execution time (response time) with configurable thresholds.   

Scope

  • Monitor the performance and availability of Applications, APIs, or links from multiple locations across your global landscape.
  • Simulate Users via recorded and customized SUM scenarios (scripts).
  • Compare factual aspects of scenario performance when scenarios are executed from different geographical locations.
  • Compare factual aspects of scenario performance over time.

Target Group

  • Application Management Service Providers and Customers who want to ensure that the applications they provide to their end users are available and perform well with respect to their corporate standards

Release Notes

SAP Focused Run 4.0 FP03

  • Monitoring UI
    • Selenium: Display the failing command in the Metrics Report section of the Execution Details.
  • Script editor
    • Migration to Java 17 (or above)

Configuration

To configure Synthetic User Monitoring carry out the following mandatory and optional steps:
 

1. Prepare the SUM Infrastructure

You configure the SUM infrastructure by performing the tasks described in the SAP Focused Run Master Guide.

Important Tasks

  • Configuration of SAP Focused Run application foundation
  • Business Scenarios of SAP Focused Run

The other configuration options – the Housekeeping and Alerting engines – are automatically configured the first time you open the Synthetic User Monitoring – Configuration section.
 

2. Register the Customer Networks for which you want to use SUM

These Customer Networks must have the status "AUM enabled" beforehand in Global Settings & Network Configuration.
 

3. Register the Monitoring Locations (Robots) for Which You Want to Deploy Scenarios

SUM Locations (robots) are Simple Diagnostic Agents (SDA) that are specially configured to execute SUM scenarios.

Any SDA connected to SAP Focused Run can be used as a SUM robot; however, it is preferable to have them located close to the end users for the application to monitor.
 

4. Import Previously Created Monitoring Scenarios (Scripts)

You can import scenarios from the User Monitoring Script Editor (which is the preferred solution – see SAP Note 2647836 to retrieve it) or directly via Synthetic User Monitoring Configuration (in the Scripts section).

You can also import existing SAP Solution Manager User Experience Monitoring (UXMon) Scripts.

In this case, they are automatically converted to the new SUM format.
 

5. Adapt the Scenario Configuration (optional)

If you import a Scenario via SUM – Configuration and the scenario requires secure parameters, these parameters must be valuated in the Scripts > Parameters section.

Other elements you can adapt include:

  • The scenario execution scheduling – in other words, how often a Script is executed (schedule.period.seconds parameter)
  • The script step thresholds
     

6. Deploy the Scenario on the Monitoring Locations

When the Scenario is deployed, the robot automatically schedules its execution as per the Scenario configuration.

Metrics start being collected, and you can visualize them on the SUM Monitoring UI.

Note that the deployment is asynchronous. It could take several minutes to become effective. SUM – Configuration indicates the deployment status in the Script Status field.
 

7. Configure SUM Alerting (optional)

By defining alerts, you can, for instance, configure automatic notifications whenever SUM detects an availability or performance problem.

Scenario Creation Best Practices

Here is a set of recommendations to keep in mind when you design an SAP Focused Run – Synthetic User Monitoring (SUM) scenario. They are applicable to all SUM scenario types.
 

Synthetic User Monitoring is a Monitoring Application

SUM is not intended for application testing or for task automation.
 

Keep your Scenario Simple

Complex scenarios are costly to create and to maintain.

It is better to have 2–3 simple scenarios rather than a single complex one.
 

Do Not Create "Disruptive" Scenarios

The execution of the SUM scenario should not negatively impact the monitored application.

Try to anticipate what could be the impact of not fully executing a scenario through to the end (e.g. in the event of availability issues).

For instance, monitoring a procurement application, a scenario booking actual items, and saving a booking could jeopardize the production system.

  • What happens if the scenario ends unexpectedly, leaving a fake booking record?
  • What happens if the scenario is simultaneously executed from ten locations, creating a shortage for booked items for the actual consumers?

For such monitoring, we recommend that you manipulate fake elements.
 

Do Not Manipulate Real-User Data

The SUM infrastructure is not designed to manipulate sensitive or personal user information within the created scenarios.

For instance, when you monitor a Sales application, you should not navigate through real sales operations. Especially if this implies navigating through personal or sensitive information related to the sales operations (such as names, credit card numbers, or account balances).
 

Do use Monitoring Users

If the scenario requires authentication when accessing the application to be monitored, do not connect with real-user accounts. We strongly recommend that you use specifically created monitoring users with no associated personal or sensitive data.

Additional Information