On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
37 rates
To enable business transaction reporting, maintain a list of match rules for your transactions under Instrumentation settings.

To add a match rule, click Add match rule. Click Edit match rule to edit existing match rules.

Add Match Rule

Define a custom match rule or automatic transaction discovery of a specified type. Automatic transaction discovery is a special match rule that automatically matches all inbound traffic of selected type, without exclusion and match detail options.

The following match rule types are supported:

  • Generic HTTP: Inbound HTTP traffic processed by SAP HTTP server
  • OData service: A subset of HTTP traffic specific for OData
  • BSP application: A subset of HTTP, but the entry point is different from that of other HTTP match rules
  • GUI transaction: Transaction codes entered by user into the command field
  • Customer Interaction Center: Front Office Processes under transaction code CIC0 (only on IS-U systems)

Match Rule Summary

A match rule consists of several settings. Match Rule Type is indicated but cannot be changed at this point. Match rules can be set to include or exclude business transactions. Include rules are always evaluated before the exclude rules, regardless of priority.

The following table summarizes other configuration settings.

FieldDescription
NameIdentifies the match rule. Business transactions matched by this rule are named by the match rule name by default. If the Name field is empty, the default naming depends on the rule type selected. If no business transaction name is resolved, the fallback transaction name "UNRESOLVED" is used. These naming rules define the base name for the business transaction splitting.
Priority

Defines the order of match rule evaluation, and bigger priority numbers are evaluated first. Without priority, match rules are evaluated in the order they appear in the list of match rules. Order of evaluation:

  1. Include rules from highest to lowest priority.

  2. Include rules without priority in list order.

  3. Exclude rules from highest to lowest priority.

  4. Exclude rules without priority in list order.

Configure Match Criteria

Match rule configuration depends on the match rule type:

Generic HTTP Match Rule

To configure a match rule:

  1. Match by HTTP request method (GET, POST, PUT, DELETE), or leave it empty to not match by HTTP request method. This value is not case-sensitive.
  2. Select the match option from the following: Equals, Starts with, Ends with, or Contains, and the set the URI pattern. The URI pattern is not case-sensitive.
    Match by URI is mandatory. 
  3. (Optional) To add match rule detail, click Add match detail. Click Edit match detail to edit existing match rule detail.

Match details check the value or existence of an HTTP parameter, header, or cookie. The values are not case-sensitive.

Set a match type and match value when checking a value, parameter, header or cookie. In the example, the match value contains a value of HTTP Parameter and is case-sensitive.
All match rule detail conditions must be met for a match to occur (AND-relation).

OData Service Match Rule 

  1. Match by HTTP request method (GET, POST, PUT, DELETE), or leave it empty to not match by HTTP request method. This value is not case-sensitive.

  2. OData service conditions are added like match rule details using Add match detail. Click Edit match detail to edit existing OData service conditions. This value is not case-sensitive. Standard F4 help is available for the OData service field.

    All OData service conditions must be met for a match to occur (AND-relation).

BSP Application Match Rule

 Match by BSP Application. This value is not case-sensitive. Standard F4 help and multi-selection are available for this field. List of BSP applications is evaluated like a standard select option (OR-relation).

GUI Transaction Match Rule

This match rule type is relevant for SAP dialog transaction monitoring. See Monitor SAP Dialog Transactions for more details. Match by Transaction Code, function code (OK code) and  application component ID. These values are not case-sensitive. Standard F4 help and multi-selection are available for Transaction Code and Application Component ID fields. All 3 lists are evaluated as a standard select-option (OR-relation).

Customer Interaction Center Match Rule

 As of release 4.5.1908 a specialized rule for Customer Interaction Center (CIC0) is available for SAP IS-U systems. It's an extension for SAPGUI match rules, which allows to split the CIC0 transaction into business transactions based on individual IS-U front-office processes

When monitoring the Customer Interaction Center only using SAPGUI match rules, all business transactions are shows as CIC0. Therefore a further splitting is needed. 

This type of match rule is only enabled when running the ABAP agent on an IS-U system. 

To match individual front-office processes, fill the selection of the most critical process you need to monitor.


Configure Transaction Splitting

When transaction splitting is active, the naming of transactions matched by the match rule can be extended. Transaction splitting depends on the match rule type:

Generic HTTP Transaction Splitting

  • First few URI segment(s)

    • Splitting value: Number of segments (N).

    • Transaction name: The first (N) of available URI segments separated by '/'. If less than (N) URI segments exist, the entire URI is used.

  • Last few URI segments(s)

    • Splitting value: Number of segments (N).

    • Transaction name: The same as the previous method, but instead of first (N) of available segments, the last (N) of available segments are used.

  • Specific URI segment(s)

    • Splitting value: The list of segments separated by ',' (Example '1,5,4,13').

    • Transaction name: The URI segments specified in the list of segments separated by '/'. Non-existing URI positions are ignored.

  • A parameter value

    • Splitting value: GET or POST parameter name (case insensitive)

    • Transaction name: "<transaction name base>." + value of parameter with specified name (if it exists in the request).

  • A header value

    • Splitting value: Header name (case insensitive).

    • Transaction name: "<transaction name base>." + value of header with specified name (if it exists in the request).

  • A cookie value

    • Splitting value: Cookie name (case insensitive).

    • Transaction name: "<transaction name base>." + value of the cookie with the specified name (if it exists in the request).

  • The request method

    • No splitting value can be set.

    • Transaction name: "<transaction name base>." + request method.

If any splitting method returns no value, the default transaction name defined by the match rule name is used instead.

OData Service Transaction Splitting

  • OData service description
    • No splitting value can be set
    • Transaction name: Technical OData service name and OData service description text in the English language.
  • OData service technical name
    • No splitting value can be set
    • Transaction name: Technical OData service name

BSP Application Transaction Splitting

  • BSP application name
    • No splitting value can be set
    • Transaction name: Technical BSP application name and BSP application description text in the English language.

If splitting method return no value and the match rule name is empty, the fallback name 'BSP' is used. 

GUI Transaction Splitting

 

  • Transaction name (Tcode)

    • No splitting value can be set

    • Transaction name: Technical Tcode name and description text in the English language.

  • Application component

    • No splitting value can be set

    • Transaction name: Technical Application component name and description text in the English language.

  • Application sub-component

    • No splitting value can be set

    • Transaction name: Technical Application sub-component name and description text in the English language.

If a splitting method returns no value, the default transaction name defined by the match rule is used instead. If the match rule name is empty, GUI Unassigned is used.

Customer Interaction Center Splitting

  • Front office process
    • No splitting value can be set
    • Transaction name: Front-office process name.

Configure Additional Snapshot Content Settings

To use Call Graphs on Linux AS (or on external Linux server), the GLIBC library needs to be at least version 4.22.

 

The SQL trace and ABAP trace can be collected and stored into a business transaction snapshot on SAP NetWeaver version greater than or equal to 7.4. This functionality is enabled or disabled with the corresponding checkbox.

ABAP trace can be customized to collect either Top 5 ABAP statements, or the complete ABAP call graph.

On SAP HANA systems, HANA expensive statements are collected when SQL trace cannot be started. The additional checkbox, Always use HANA expensive statements, is available for SAP HANA systems that, when enabled, omits SQL trace completely. HANA expensive statements must be enabled and a meaningful threshold must be set in t-code DB02.
Custom actions functionality can be globally enabled or disabled with the corresponding checkbox.

SAP usernames can be excluded from business transaction snapshots with the corresponding checkbox.

Limit Transaction Detection for Specific Users

For testing purposes, you can set up a white-list of users for which the business transaction detection is enabled.

Click BT user filter in the AppDynamics settings toolbar. Following figure shows sample list of usernames.

Automatic Downstream Correlation With Incoming Traffic

From version 4.4.1812.0 onward, incoming HTTP requests that contain a valid correlation header are automatically correlated and the business transaction is continued even without any Generic HTTP, OData or BSP match rules. A match rule was needed to achieve this in previous versions.

  • No labels