(DI-2308) Collector for Workload Statistics (STAD 5 Min)
- SNP
The technical name of this collector is /DVD/MON_STAT_CL_COL_WORKLOAD.
This collector mainly serves to provide information through detail table. It collects two kinds of details. First are database operation details (roll, wait, read times, etc.) The second detail is 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 RFC | Number | Yes |
STAD_DB_DIALOG_AVG | Average Response Time for Users on Database | ms | No |
STAD_DB_RESP_AVG | Average Response Time on Database | ms | No |
Parameters
The following parameters are used for this collector:
Parameter name | Description |
|---|---|
AGGREGATION_TIME_S | Affects the detail table. States number of seconds for aggregation/grouping of STAD rows. Default 300 seconds (5 minutes). For example if in 300 seconds are 3 same calls made, they will be grouped and reported in a single row of detail table. |
LOAD_STAD_REC_BY_ONE_SERVER | This parameter defines if the STAD records are loaded and processed simultaneously for all application servers or sequentially one by one application server. By default, this value is empty, so the STAD records are loaded and processed simultaneously for all application servers. If this value is set to 'X', the STAD records are loaded and processed sequentially one by one application server. This approach is only useful if there are too many application servers on the system and processing too many STAD records simultaneously is causing the runtime errors due to the low memory on the system. |
WAIT_FACTOR | Value is inversely proportional to wait time for aRFC callbacks of 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. Wait time is calculated using the following expression: 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, as SAP introduced a new parameter in function SWNC_STAD_READ_STATRECS which suppress the wait factor value. Default value: 30 |
Detail table
The collector provides two detail tables. First is Workload statistics transaction jobs. It provides details from STAD for transaction jobs. The technical name of the table is /DVD/MON_STAT_T_APPD
Technical name | Description |
|---|---|
EVENT_TIMESTAMP | Event timestamp |
SID | System ID |
SAP_APPLICATION | Application |
SUBAPPLICATION | Sub Application |
COMPONENT | Component |
PACKAGE | Package |
CLIENT_CODE | Client (MANDT) |
SERVER | Server name |
REPORT_OR_TRANSACTION | Object Name in Object Directory |
OBJECT_TYPE | Object type (report or transaction) |
JOB_NAME | Name of job |
TASK_TYPE | Task type (dialog, background, etc.) |
USER_NAME | User name |
STEP_COUNT | Number of steps |
LUW_COUNT | LUW count |
RESPONSE_MS | Response in ms |
PROCESSING_MS | Processing in ms |
CPU_MS | Time spent on CPU |
DB_MS | Time spent on DB |
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 ms |
SEQUENTIAL_READ_REC | Sequential reads of *REC statements |
DIRECT_READ_COUNT | Number of direct reads |
DIRECT_READ_MS | Time of direct reads in ms |
DIRECT_READ_REC | Direct read of *REC statements |
LOGICAL_CHANGE_COUNT | Number of logical changes |
LOGICAL_CHANGE_MS | Time of logical changes in ms |
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 DB |
DB_PROCEDURE_MS | Time of DB procedure calls |
GUI_NETWORK_MS | Time spent on GUI during the network in ms |
GUI_MS | Time spend on GUI in total in ms |
ROUNDTRIP_COUNT | Number of complete calls (back and forth) |
REQUESTED_DB_BYTES | Requested bytes |
DATA_TO_APPL_BYTES | Bytes to application processing |
DATA_TO_GUI_BYTES | Bytes for GUI processing |
VMC_CALLS | Number of VMC calls |
VMC_CPU_MS | Time of VMC calls in ms |
VMC_ELAPSED_MS | VMC elapsed calls in ms |
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 table is /DVD/MON_STAT_APPD_RFC.
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 | States if its report/transaction |
OBJECT_TYPE | Object type |
USER_NAME | User name |
DIRECTION | Directing (Out/In) |
RFC_DESTINATION_NAME | RFC destination name |
RFC_USER_NAME | User name in RFC call |
RFC_CALL_COUNT | Number of times called this same RFC |
RFC_EXECUTION_MS | RFC execution time in ms |
RFC_CALL_MS | RFC call in ms |
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 |