Front-end monitoring - SAP GUI

In the SAP GUI section you set parameters specific to monitoring SAP GUI-based software services.

SAP GUI - general

Use the SAP GUI analyzer to configure the monitoring of communication between a SAP GUI Windows client and a SAP application server.

Most SAP GUI monitoring parameters are adjusted globally, which means that you can create most basic parameters for software monitoring when you create user-defined software services.

To change SAP GUI monitoring settings, open NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, Global ► Front-End Monitoring ► SAP GUI.


  • Max filtered string length
    The NAM Probe filters DIAG traffic in a search for strings containing a meaningful operation or user information. The SAP GUI parser processes command chunk content to clean irrelevant or random strings out of the traffic data. This configuration property tells the parser to remove strings or character combinations shorter than or equal to this value.
    Default: three bytes (three characters).
  • Safe Threshold
    Use this option to exclude long-executing operations (in minutes) from average measurements. This improves the precision of reporting for typical interactive operations while maintaining the full scope of SAP transaction monitoring. Operations longer than the value set in Safe Threshold will be excluded from average measurements.
  • Max idle time
     If the idle time between hits is greater than limit set here, the hits will be assigned to separate operations. Default: 45 seconds
  • SAP server time method
    Define the method of calculating the server time for SAP GUI. This impacts reports showing metrics for the operations, hits and aggregate metrics for operations and hits.
    • first – The server time from the first observed operation is reported.
    • last – The server time from the last observed operation is reported.
    • average – The average server time based on all observed operations is reported.
    • max – The maximum server time from all observed operations is reported.
    • sum – The sum of all operation server times is reported.

Operation and User Name recognition

  • Recognize User Names
    Select to automatically recognize the user name based on default user name chunk ID: 16.4.28.
  • User name chunk ID
    The chunk ID string contained in the command chunk that also contains the user name. This may vary depending on the server. Default value is 16.4.28. You can use regular expression to operate on the user name parts for a given chunk ID. Enter a regular expression that enables you to filter the user name. Regular expressions may be useful for cutting out the irrelevant or unnecessary parts of names. Use POSIX Basic Regular Expressions syntax.
  • Operation name chunk IDs
    The chunk ID string contained in the command chunk that also contains the transaction code (T-Code). Default: 16.6.7

The differences in configuration of SAP GUI monitoring in earlier NAM Probe versions create a variant that can be only applied to current version. The NAM Console will automatically display the configuration that applied to the particular NAM Probe version.

Current NAM Probe configuration

The following configuration options are available.

Attribute/Metric/Parameter definition

Monitoring T-Code alone is often not enough to pinpoint performance problems, especially when complex SAP transactions are performed. You can identify and report SAP operations based on context retrieved from specific SAP form fields. To do this, you will need to define a field value to be retrieved from selected SAP form fields.

This table presents definitions for each configured value. It summarizes how the value should be extracted, where should it be reported and as what should the value be reported. Use the right-click to open the context menu and choose Add, Open or Delete.

  1. Choose how value should be reported
    Define how the extracted value should be reported.
  2. Choose where given value should be reported
    Select the group based on automatically detected sets of operation attributes.
  3. Configure how value should be extracted
    Select the value extraction method:
    • Chunk ID
      You can select which chunk ID will be used to extract the value. The value will be later appended to the T-Code by the report server when SAP GUI data is reported. By default Window Status (also referred to as window title) chunk ID is selected. (16.6.16).
    • Form ID
      Enter the SAP form ID that should be used to extract the value from selected SAP form fields.
    • SAP GUI RFC Exception
      SAP GUI traffic can contain information on RFC Exceptions and Errors. Selecting this option, you define the extracted value as a Remote Function Call (RFC) exception.
    • SAP GUI RFC Error Message
      Selecting this option, you define the extracted value as a RFC Error Message. Default configuration of RFC errors is applied.
  4. Define if given elements occur more than once.
    Select which of the values should be taken under consideration. Detected First, Last or All detected values.
  5. Optionally, you can enter excluding regular expression that will reject all objects matching this regex. This excluding regex is optional but it proceeds the including regex.
  6. Optionally, you can enter a regular expression that will be applied to the extracted value. This regex will be applied to remainder of the excluding regex.
  7. Search scope:
    Select to which observed traffic the regular expression search should be applied: response, request or both.

SAP GUI - availability

By configuring the availability, you can determine which attempt failures are included in the availability metric calculation.

The availability is measured and presented as the percentage of successful attempts (operations) compared to all attempts. Each attempt is counted in one metric: operation, standalone, abort, network failure, transport failure or application failure. All operations with availability problems are included in the Failures (TCP), Failures (transport) and Failures (application) metrics.

You can configure SAP GUI availability globally or at the software service level.

For global configuration, open the NAM Probe configuration and go to Global ► Front-End Monitoring ► SAP GUI ► Availability. For the software service level, select the Availability tab in the Edit Rule window.

Failures (transport)

You can determine whether two of the incomplete response types, No response and Partial response errors should be included in the calculation of Failures (transport) metric.

Failures (applications)

Enable or disable the automatically detected operation attributes to individually select which sets of operation attributes are included in the calculation of Failures (application) . The following operation attributes are available:

  • SAP GUI status error
  • SAP GUI error indicator
  • Window title
  • Operation attributes (4)
  • Operation attributes (5)

Note that by default Window title attribute is always present, so it is not recommended to enable it as a failure as it will cause 0% of availability reported.

All of these are configurable in the general settings.

SAP GUI - fault domain isolation

Use the following threshold settings to accurately identify the true source of the problem:

Server time threshold
The Server time threshold relates to the server time portion of an overall operation time. Server times above the threshold limit are considered to be slow due to poor data center performance.

Idle time threshold
Threshold for the time during the operation execution when there is no network or server activity related to the operation. It is assumed that Idle time is caused by the user's software not sending requests because user's PC is busy.

Network time threshold
Threshold for the time the network (between the user and the server) takes to deliver requests to the server and to deliver page information back to the user. In other words, Network time is the portion of transaction time that is due to the delivery time on the network.

Retransmissions threshold
Percentage of retransmissions regarding all observed transmissions.

Network time affected by high retransmission threshold
Percentage of the network time affected by high retransmission threshold.

Request size threshold Threshold for the request where anything larger would be considered big request.

Network time affected by the transfer of a big request threshold
Threshold for the request where anything larger would be considered big request.

Response size threshold
Threshold for the response where anything larger would be considered big response.

Network time affected by the transfer of a big response threshold
Threshold for the network time that is affected by the transfer of a big response threshold.

Number of hits threshold
Threshold for the number subcomponents of error-free operations or transactions.

Single hit duration threshold
Threshold for a hit duration as a percentage of operation time.

Rtt threshold
Threshold for the time it takes for a SYN packet to travel from the client to a monitored server and back again.

For more information