Collector for Workload Statistics (STAD 5 Min.)
The technical name of the Collector for Workload Statistics (STAD 5 Min.) is /DVD/MON_STAT_CL_COL_WORKLOAD.
This collector collects two types of details:
-
Database operation details (roll, wait, read times, etc.)
-
RFC statistics (execution time, call time, transmitted data, etc.)
Default KPIs Delivered with This Collector
This collector collects only one KPI:
KPI name |
Description |
Unit |
Detail table |
---|---|---|---|
STAD_INBOUND_RFC_COUNT |
Number of all inbound RFCs (APPD STAD MAIN) |
Number |
Yes |
Parameters
The following parameters are used for this collector:
Parameter name |
Description |
---|---|
AGGREGATION_TIME_S |
Affects the detail table. Defines the number of seconds used for the aggregation/grouping of STAD rows. Default value: 300 seconds (5 minutes) For example, if three of the same calls are made in 300 seconds, they will be grouped and reported in a single row of the detail table. |
LOAD_STAD_REC_BY_ONE_SERVER |
This parameter determines whether the STAD records are loaded and processed simultaneously for all application servers or sequentially, one application server at a time. By default, this value is empty, so the STAD records are loaded and processed simultaneously for all application servers. NOTE If this value is set to X, the STAD records are loaded and processed sequentially one application server at a time. This approach is only useful if there are too many application servers on the system and processing too many STAD records simultaneously causes runtime errors due to the low memory on the system.
|
WAIT_FACTOR |
This value is inversely proportional to the wait time for aRFC callbacks of the function module SWNC_STAD_READ_STATRECS. The function module calls each application server using aRFC, and the wait factor determines how long the logic waits for all aRFC calls to complete. The wait time is calculated using the following method: wait_time = read_time / wait_factor + 20 On higher SAP releases (SAP_BASIS 740: SP 0017 and higher), it does not make sense to change the value of this parameter, because SAP introduced a new parameter in the function SWNC_STAD_READ_STATRECS that suppresses the wait factor value. Default value: 30 |
Detail Table
The collector provides two detail tables. The first one is Workload statistics transaction jobs. It provides details from STAD for transaction jobs. The technical name of the detail table is /DVD/MON_STAT_T_APPD. It contains the following fields:
Technical name |
Description |
---|---|
EVENT_TIMESTAMP |
Event timestamp |
SID |
System ID |
SAP_APPLICATION |
Application |
SUBAPPLICATION |
Subapplication |
COMPONENT |
Component |
PACKAGE |
Package |
CLIENT_CODE |
Client (MANDT) |
SERVER |
Server name |
REPORT_OR_TRANSACTION |
Object name in the object directory |
OBJECT_TYPE |
Object type (report or transaction) |
JOB_NAME |
Job name |
TASK_TYPE |
Task type (dialog, background, etc.) |
USER_NAME |
Username |
STEP_COUNT |
Number of steps |
LUW_COUNT |
LUW count |
RESPONSE_MS |
Response in milliseconds |
PROCESSING_MS |
Processing in milliseconds |
CPU_MS |
Time spent on the CPU |
DB_MS |
Time spent on the database |
ROLL_WAIT_MS |
Time spent for roll + wait |
WAIT_MS |
Wait time |
SEQUENTIAL_READ_COUNT |
Number of sequential reads |
SEQUENTIAL_READ_MS |
Time of sequential reads in milliseconds |
SEQUENTIAL_READ_REC |
Sequential reads of *REC statements |
DIRECT_READ_COUNT |
Number of direct reads |
DIRECT_READ_MS |
Time of direct reads in milliseconds |
DIRECT_READ_REC |
Direct read of *REC statements |
LOGICAL_CHANGE_COUNT |
Number of logical changes |
LOGICAL_CHANGE_MS |
Duration of logical changes in milliseconds |
LOGICAL_CHANGE_REC |
Logical changes for *REC statements |
LOGICAL_ABAP_CALLS |
Number of ABAP calls |
PHYSICAL_READ_COUNT |
Physical memory read count |
PHYSICAL_CHANGE_COUNT |
Physical memory change count |
DB_PROCEDURE_CALLS |
Number of procedure calls on the database |
DB_PROCEDURE_MS |
Time of database procedure calls |
GUI_NETWORK_MS |
Total front end network time in milliseconds |
GUI_MS |
Time spent on the GUI in total in milliseconds |
ROUNDTRIP_COUNT |
Number of complete calls (sent and received) |
REQUESTED_DB_BYTES |
Requested bytes |
DATA_TO_APPL_BYTES |
SAP workload: Ø data volume to application server (byte) |
DATA_TO_GUI_BYTES |
SAP workload: Ø data volume to front end per step (byte) |
VMC_CALLS |
Number of VMC calls |
VMC_CPU_MS |
Time of VMC calls in milliseconds |
VMC_ELAPSED_MS |
VMC elapsed calls in milliseconds |
TEXT |
Short description |
TOP_TAB1 |
Top processed table |
TOP_TAB2 |
Top processed table |
TOP_TAB3 |
Top processed table |
TOP_TAB4 |
Top processed table |
TOP_TAB5 |
Top processed table |
The second detail table is Workload statistics RFC. This detail table collects details about RFC calls. The technical name of the detail table is /DVD/MON_STAT_APPD_RFC. It contains the following fields:
Technical name |
Description |
---|---|
EVENT_TIMESTAMP |
Event timestamp |
SID |
System ID |
CLIENT_CODE |
Client (MANDT) |
SERVER |
Server name |
RFC_FUNCTION_NAME |
RFC function module name |
RFC_PROGRAM_NAME |
RFC program name |
REPORT_OR_TRANSACTION |
Whether the RFC call is a report or a transaction |
OBJECT_TYPE |
Object type |
USER_NAME |
Username |
DIRECTION |
Direction (outbound or inbound) |
RFC_DESTINATION_NAME |
RFC destination name |
RFC_USER_NAME |
Username in the RFC call |
RFC_CALL_COUNT |
Number of times his same RFC has been called |
RFC_EXECUTION_MS |
RFC execution time in milliseconds |
RFC_CALL_MS |
RFC call time in milliseconds |
RFC_CALLING_INSTANCE |
RFC calling instance |
RFC_CALLING_IP_ADDRESS |
RFC target IP |
RFC_CALLING_RELEASE |
RFC target release |
DATA_SEND_BYTES |
Sent bytes |
DATA_RECEIVE_BYTES |
Received bytes |