Synthetic User Monitoring

Synthetic User Monitoring (SUM) is an application of the Focused Run – Advanced User Monitoring (AUM) use case.

Synthetic User Monitoring 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

Focused Run 1.00 Feature Pack 02

  • Monitoring of Performance and Availability for HTTP and SAPGUI Scenarios
  • Monitoring UI
    • Status Overview
    • Scenario and Location Tree Views
    • Performance View
    • Status View
  • Configuration
    • Import of SAP Solution Manager - User Experience Monitoring (UXMon) scenarios

Focused Run 1.00 Feature Pack 03

  • Alerting for the Performance or the Availability
    • Highly configurable
    • For single Scenario or Location
    • For groups of Scenarios/Locations
    • Automatic reaction with Notifications and/or Outbound connection
  • Monitoring UI
    • Geomap view to have an of the Monitoring Locations state
    • Advanced layout management to create better customer pages
    • Improved Scenario and Location Tree Views to ease the handling of larger time ranges

Focused Run 2.00

This release provides the following enhancements:

  • Monitoring UI
    • New Status Statistics view to ease the analysis of status evolution over long time ranges

  • Configuration
    • New "Cron-based" execution scheduling
    • Improved Script Editor

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 Focused Run Master Guide.

Important tasks here are:

  • Configuration of Focused Run Application Foundation
  • Business Scenarios of Focused Run – Advanced User Monitoring

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

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 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.