SAP GUI End User Monitoring (EUM) collects details about user actions in SAP Dialog Transactions. Collected details are transmitted to AppDynamics controller via IoT REST API. Details are presented in the AppDynamics controller via 'Connected Devices' section. Monitoring provides overview of user sessions and interactions with the SAP system (network requests) and SAP GUI runtime errors.

Controller supportability

IoT Monitoring is currently available only for AppDynamics SaaS controllers.

Beta

This feature is currently available as Beta. Please review the "Beta Agreement for SAP GUI EUM" in the release zip file for specific terms and conditions.

Prerequisites

Configure SAP GUI Instrumentation

You can customize SAP GUI Instrumentation from Instrumentation settings > SAP GUI Instrumentation using SAP transaction code /DVD/APPD_CUST.

The following table describes the fields and descriptions for SAP GUI Instrumentation:

FieldDescription
IoT Host

IoT REST API Base URL used to push IoT data from ABAP Agent to AppDynamics Controller / Analytics.

If you use HTTPS, you will need to download certificates from IoT Host via browser and import them into the STRUST identity you use for AppDynamics. See SSL Certificates.

API KeyIoT API Key generated during creation of 'Connected Devices' application. See prerequisites.
Validation Mode

When active, validation mode checks each IoT beacon created by ABAP Agent before it is submitted to the IoT Host.

Validation Mode is intended mainly for troubleshooting and support purposes and should be turned off otherwise.

Split by system name

When active, data from the system be grouped by the SAP system ID (SID) under the 'Connected Devices' application. When deactivated, the data will be grouped under SAPGUI.

EUM Correlation is Active

When active, SAP GUI EUM data are correlated to APM business transactions and business transaction snapshots.

SAP GUI Instrumentation is ActiveUsed to activate / deactivate SAP GUI Instrumentation functionality.

Optional steps

User data are anonymized by default.

To see real SAP User IDs and Terminal IDs, you need to turn off anonymization of user data under Snapshot settingsUser Data. See Configure Snapshot Settings.

Validate Configuration

Once SAP GUI Instrumentation is configured and active, connection status can be checked using transaction /DVD/APPD_STATUS.

Open the controller UI and navigate to User Experience → Connected Devices. If everything is configured correctly, the SAP system ID (or SAPGUI) should appear under application of choice.

Troubleshooting

There are three main errors that can happen after setting up SAP GUI Instrumentation:

  1. Connection failed

    Make sure that the URL for the IoT Host is correct (https://iot-col.eum-appdynamics.com/ or different region-specific value). Also, check with SAP basis and network team that this host is not blocked by firewall/network policy.
  2. Invalid key

    Check if the API Key exists on the controller and if it is correctly entered in Instrumentation. API Key is case sensitive so make sure it is all uppercase in SAP GUI.
  3. Invalid certificate

    Make sure that the certificate from that host is successfully imported into the STRUST identity you are using for AppDynamics according to this guide. Used STRUST identity can be found via transaction /DVD/APPD_CUST.

Overview

Here is a basic overview of SAP GUI End User Monitoring.

Devices and Users

This section provides basic overview of all connected devices. Each SAP terminal is replicated as a “Unique Device”. The following details are available:

Widget Description
EventsTime series of all SAP GUI user interactions with the instrumented SAP systems.
Active DevicesNumber of unique SAP terminals connected to instrumented SAP systems that interact with the systems during selected time period.
Unique DevicesList of all SAP terminals connected to instrumented SAP systems that interact with the systems during selected time period with corresponding SAP User name and SAP GUI version (firmwareversion).
UsersPie chart of top X SAP users sorted by the number of their interactions (events). 
Event Types

Number of events per event type.

  • Network request - standard user interaction with an SAP system via SAP GUI session.
  • Error - user interaction with an SAP system via SAP GUI session terminated with a runtime error.

Double-clicking on a unique device row displays an activity stream for the selected SAP terminal.

Device details show SAP system ID (or SAPGUI) under Device Type based on 'Split by system name'.  When correlation is activated, events in the activity stream are correlated to existing business transactions. If a snapshot exists, navigation to event-specific business transaction snapshot is possible. Clicking of individual events displays additional details like SAP transaction code, client code, function code, report name, etc. Error events contain info about the runtime error.

Network Requests

This section provides more detailed overview of all network requests (user interactions with instrumented SAP systems via SAP GUI).

Widget Description
Network RequestsList of events aggregated by the Network Request Name value.
Top 5 actionsTop 5 user actions (executed function code in a specific SAP transaction) in the current time frame.
Network Request TimeTime series of event request times.
Network Request Duration DistributionDistribution visualization of network requests by event duration.
Application VersionSAP GUI version distribution.
Network Request EventsNon-aggregated list of events.
Top Network ErrorsList of most frequent errors.

Errors

This section provides more detailed overview of all error requests (user interactions with instrumented SAP systems via SAP GUI ending in runtime errors).

Widget Description
ErrorsLists of errors aggregated by the Error Name value.
Errors Per XDistribution of errors by OS Version and Firmware (SAP GUI) Version.
Total X

Count and distinct count.

Errors Over TimeTime series of error occurrences.
Error EventsNon-aggregated list of all error events.