AppDynamics for SAP allows performance monitoring of SAP dialog transactions performed by users using the SAP GUI application. Customize the monitoring for selected T-codes or for application components such as FI-GL. See Configure Business Transaction Detection.
Performance Data Collection
The performance data is collected from SAP STAD statistics every minute in the background. This data is aggregated on application component or sub-component level.
Business Transaction Snapshots
A transaction snapshot is taken when the response time of a dialog step exceeds the baseline. It contains detailed information from the statistical records, such as T-Code, program, DB time, ABAP time, and wait time.
To include DB table statistics into the snapshot, enable collection of the following statistics in transaction ST03:
- Start transaction ST03(N).
- In the menu left navigate to Collector and Performance DB >> Statistics records and files >> Online parameters >> Dialog step statistics.
- Set the parameter
5to enable collection of performance data for top five DB tables.
A sample Snapshot with top 5 DB tables:
RFC Exit Call Detection
Synchronous and asynchronous RFC calls performed during dialog transactions are collected and displayed as exit calls in transaction dashboard:
If the remote SAP system (RFC target) is instrumented using the ABAP agent, the business transaction is correlated with the calling system and the snapshot contains information from both systems:
If the remote SAP system is not instrumented, the exit call is displayed without target tier and drill down is not possible:
The correlation information is passed from the caller system to the remote system using AppDynamics function module through the same RFC destination as the detected RFC call. The user of the RFC destination needs the authorization to call AppDynamics RFC function modules. To enable the correlation, assign the role
/DVD/APPD_USER to all RFC users.
Currently only RFC destinations to ABAP systems are supported.
When a dialog transaction crashes or ends with an ABAP short dump, the error description is stored in the snapshot. The transaction is marked as an error.
If a dialog transaction starts an asynchronous update task which fails, the update error (as displayed in transaction SM13) is included in the snapshot. The transaction is marked as an error.
As of release 4.4.1812 of the ABAP agent the SAP GUI monitoring supports correlation of business transactions with SQL trace data (ST05). This is available only for SAP systems with release higher than 7.40.
Currently the SQL trace is not started automatically, you need to activate it manually in transaction ST05.
If you see a business transaction performance issues and the snapshots contain high DB response times, start transaction ST05 in the SAP system and activate the SQL trace for problematic T-code and/or user.
Let the SQL trace active for couple of minutes to collect the data for the business transaction. Make sure you activate the trace when the business transaction is being used or start the transaction on your own.
When the ABAP agent takes the business transaction snapshot and finds SQL trace measurements, it automatically correlates the ST05 records with the business transaction and adds longest SQL statements into the snapshot: