Configure Snapshot Settings

Business transaction snapshot content can be adjusted using snapshot settings. To access this screen, navigate to t-code /DVD/APPD_CUST → Instrumentation and select Snapshot settings tab.

User Data

• Collect user data - SAP user names and terminal IDs are added to business transaction snapshots. SAP user names are added to application events and analytics data.
• Collect anonymized user data - same as the previous option, but the values are anonymized via hash function.
• Don't collect user data - business transaction snapshots, out-of-box events and analytics data will not contain any user data.

To maintain user data (PII) filter for custom events and analytics data, see User Data Filter.

SQL Trace

• Collect SQL trace (Top 5 statements) - SQL trace (ST05) can be collected and stored into a business transaction snapshot as Top 5 SQL statements.

• Always collect SQL trace from HANA expensive statements - On SAP HANA systems, HANA expensive statements are collected when SQL trace cannot be started. This checkbox is available only on SAP HANA systems. When enabled, SQL trace (ST05) is omitted completely. HANA expensive statements must be enabled via HANA configuration and a meaningful threshold must be set in t-code DB02. Also, see HANA Expensive Statements Setup.
• Resolve SQL condition values when available - SQL statements are added to business transaction snapshots without resolved variables. This behavior can be overridden using this checkbox.
• Use proactive SQL tracing for GUI transaction - Added in release 20.8.0. When enabled, SAP GUI monitoring will start SQL trace when it detects slow SAP GUI session. Only one t-code can be traced per application server per minute. As of release 20.11.0, this trace will force the BT to create a snapshot.

  
  

  

  As of version 22.11.0, this option is hidden on systems with primary HANA database. This functionality is substituted by HANA expensive statements. If this option is enabled before upgrading to version 22.11.0, it will be hidden once you manually deactivate it.

ABAP Trace

• Collect ABAP trace (Top 5 statements) - ABAP trace (SAT) can be collected in aggregated mode and stored into a business transaction snapshot as Top 5 ABAP statements.
• Collect ABAP trace (Call Graphs) - ABAP trace (SAT) can be collected in non-aggregated mode and added to a business transaction as a call graph.
  

• Collect Call Graphs and Top 5 statements - ABAP trace (SAT) can be collected in non-aggregated mode plus aggregated mode and added to a business transaction as a call graph and Top 5 ABAP statements. This option uses a custom ABAP trace file parser with much-improved performance compared to the SAP standard parser used by the other two options.
  

  

  To use Call Graphs on Linux AS (or on external Linux server), the GLIBC library needs to be version 2.17 or later

• Don't use ABAP trace - don't use ABAP trace.
• Use proactive ABAP tracing for GUI transaction - When enabled, SAP GUI monitoring will start ABAP trace when it detects slow SAP GUI session. Only one t-code can be traced per application server per minute. Resulting trace is processed in non-aggregated mode. This trace will force the BT to create a snapshot.
  

Other Settings

• Include custom actions into snapshots - Custom actions functionality can be globally enabled or disabled with this checkbox.