Default KPIs for SAP Systems

APP_LOGS

Number of application logs specified by rules

Count

SAPSYS

This KPI displays a template definition that can be used to calculate the number of application logs. To start the monitoring of this KPI, you must assign this KPI to the monitoring profile and insert it into the input table /DVD/MON_ALOG_I2. In this input table, you can define various settings based on which the specific application logs will be included in this KPI value.

Remote system

System

Any server 

/DVD/MON_CL_COL_APPLOG

N/A: You must schedule this KPI manually*

ARFC_FREE

Number of available (free) WP for aRFC resources

Count

SAPSYS

This KPI displays the resources of an application server. It collects the number of available work processes for asynchronous RFC resources. For more information, see the page https://help.sap.com/saphelp_nw70ehp2/Helpdata/en/7f/06363dc992752de10000000a114084/frameset.htm

Remote system

Server

Only application server

/DVD/MON_CL_COL_ARFC

DEF_5MIN

ARFC_FREE_P_MIN

Minimum of percentage of available WP for aRFC

%

SAPSYS

This KPI displays the minimum percentage value of free work processes from all application servers. Each application server has a configured number of work processes that are used for asynchronous RFC resources.

Central system

System

Any server

/DVD/MON_CL_COL_ARFC

DEF_5MIN

BAT_DB_INSERT_AG

Average DB insert

ms

BENCH

This KPI displays the database insert time of the benchmark as an average of collected values for this KPI in the last 60 minutes. This is a database mini-benchmark for insert workload (insert SQL). It is a standard, repeatable mini-workload to measure database-wide performance differences. The collector inserts N entries from an internal table (N is 10.000 entries by default). If needed, you can change this value with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB.

Remote system

System

Any server

/DVD/MON_BAT_CL_DB

DEF_5MIN

BAT_DB_SELECT_AG

Average DB select

ms

BENCH

This KPI displays the database select time of the benchmark as average of collected values for this KPI in the last 60 minutes. This is a database mini-benchmark for read (select SQL). It is a standard, repeatable mini-workload to measure database-wide performance differences.
This select uses a WHERE clause on the primary key, for example to select all N entries (N is 10.000 entries by default). If needed, you can change this value with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB.

Remote system

System

Any server

/DVD/MON_BAT_CL_DB

DEF_5MIN

BAT_DB_UPDATE_AG

Average DB update

ms

BENCH

This KPI displays the database update time of the benchmark as an average of collected values for this KPI in the last 60 minutes. This is a database mini-benchmark for updates (update SQL). It is a standard, repeatable mini-workload to measure database-wide performance differences.
The updates use a WHERE clause on the primary key, for example to update single non-key fields for N entries (N is 10.000 entries by default). If needed, you can change this value with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB.

Remote system

System

Any server

/DVD/MON_BAT_CL_DB

DEF_5MIN

BTC_NUM_DELAYED

Number of delayed background jobs ( >= 60 seconds)

Count

SAPSYS

This KPI displays the number of background jobs that have been waiting for free work process for more than 60 seconds. By default, this KPI includes only jobs that have not start yet, but are currently waiting for a free work process and are still in delayed state.

If you want to monitor jobs that were waiting for a free work process since the last run of the collector without checking its starting condition, you can disable the collector parameter ONLY_NOT_STARTED_AS_DELAYED by setting its value to space. If this parameter is disabled, in this KPI are included all jobs that were in delayed state, but can be already running or finished in the last snapshot.

Remote system

System

Any server

/DVD/MON_CL_COL_BG_JOBS

DEF_5MIN

BTC_NUM_LONGRUN

Number of background jobs running too long ( >= 10 minutes)

Count

SAPSYS

This KPI displays the number of background jobs that have been running for more than 10 minutes.

Remote system

System

Any server

/DVD/MON_CL_COL_BG_JOBS

DEF_5MIN

Any server

Any server

CPU_LOAD15

CPU load (15 min): Average of active processes

Count

OS

This KPI displays the CPU load average. This is the average number of processes that are currently being executed or waiting to be executed by the CPU in the operating system run queue over the last 15 minutes.

In SAP, you can view this KPI via transaction OS07; in Linux, with the uptime command.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

N/A: You must schedule this KPI manually*

CPU_LOAD1_P

CPU load (1 min): Percentage of CPUs for active processes

%

OS

This KPI displays the CPU load average as a percentage. This is the average number of processes that are currently being executed or waiting to be executed by the CPU in the operating system run queue in the last minute.

In SAP, you can view this KPI via transaction OS07; in Linux, with the uptime command.

This KPI displays the percentage of the CPU load average in the last minute divided by the number of existing CPUs. High numbers indicate potential overloads of the CPUs. On hardware with multi-threaded CPUs, the number of logical CPUs is used.

Example: An IBM Power-8 using two processors with SMT-8 results in 16 logical CPUs. Processor saturation and application slowdown for non-threaded applications can be reached earlier on multi-threaded CPUs and must be considered when making decisions.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_1MIN

CPU_LOAD5

CPU load (5 min): Average number of active processes

Count

OS

This KPI displays the CPU load average. This is the average number of processes that are currently being executed or waiting to be executed by the CPU in the operating system run queue over the last 5 minutes.

In SAP, you can view this KPI via transaction OS07; in Linux, with the uptime command.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

CPU_LOAD5_PMAX

CPU load (5 min): Maximum % of CPUs for active processes

%

OS

This KPI displays the maximum percentage of CPUs for active processes from all existing servers for one SAP system (the highest value is reported). It is based on the KPI CPU_LOAD5_P.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

CPU_SYS

CPU: Used by system

%

OS

Percentage usage of CPU used by system on a specific server.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

CPU_USER

CPU: Used by user

%

OS

This KPI shows the used CPU by user based on statistics in transaction ST06.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

CPU_WAIT

CPU: I/O wait

%

OS

I/O wait utilization accrues when the CPU would be able to do some work, but all processes on the CPU are waiting for I/O responses. In SAP, you can see this indicator with OS07. Values are collected for the database and for all application servers. The chart displays only the worst value (usually the I/O wait of the database; the I/O wait on the application server is usually zero).

Remote server

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

CTS_AGE_OLDESTRQ

CTS – Age of the oldest request in queue

min

SAPSYS

This KPI displays the age of the oldest transport request in queue.

Remote system

System

Any server

/DVD/MON_CL_COL_CTS

DEF_1DAY

CTS_RC0000A

CTS – Number of imported transports

Count

SAPSYS

This KPI displays the total number of imported transport requests.

Remote system

System

Any server

/DVD/MON_CL_COL_CTS

DEF_1DAY

CTS_RC0008A

CTS – Number of imported transports with RC >= 8

Count

SAPSYS

This KPI displays the number of imported transport requests with RC = 8.

Remote system

System

Any server

/DVD/MON_CL_COL_CTS

DEF_1DAY

This KPI displays the total number of all configured ABAP daemons on the application server.

ABAP daemons provide a concept similar to Linux cron jobs or Windows services. Once started, there is no limit for the lifetime of ABAP daemon sessions. Applications can use daemons to handle events in a reliable way and keep a state in between. Contrary to other session types, such as HTTP, GUI or RFC sessions, ABAP daemon sessions are robust against errors, i.e. a daemon session is immediately restarted after an error occurs (E/A/X messages).

This KPI displays the number of new events in the ABAP daemons running on the application server. It calculates the delta of events since the last collector execution.

ABAP daemons provide a concept similar to Linux cron jobs or Windows services. Once started, there is no limit for the lifetime of ABAP daemon sessions. Applications can use daemons to handle events in a reliable way and keep a state in between. Contrary to other session types, such as HTTP, GUI or RFC sessions, ABAP daemon sessions are robust against errors, i.e. a daemon session is immediately restarted after an error occurs (E/A/X messages).

This KPI displays the number of ABAP daemons that have the status Died on the application server.

ABAP daemons provide a concept similar to Linux cron jobs or Windows services. Once started, there is no limit for the lifetime of ABAP daemon sessions. Applications can use daemons to handle events in a reliable way and keep a state in between. Contrary to other session types, such as HTTP, GUI or RFC sessions, ABAP daemon sessions are robust against errors, i.e. a daemon session is immediately restarted after an error occurs (E/A/X messages).

DELAY_LAST_RUN

Delay since last successful run

min

SAPSYS

This KPI measures the last successful run of the collector job. If some jobs are hanging or running in a never ending loop, the next collector will not be started. This KPI displays the time of the last successful completion of the collector job.

Central system

System

Any server

/DVD/MON_CL_COL_SYSTEM

DEF_1MIN

DB_CRIT_TAB_SP_P

Used space on most critical data file (tablespace)

%

DB

This KPI displays the percentage of used space that the most critical data file on the database occupies, i.e. the data file that uses the most space. The most critical data file (tablespace) is chosen by size. The data file with the smallest free size to extend is considered to be the most critical file. For files that do not have a maximum size defined, the size of the logical device on which the file resides is used. The percentage is then calculated based on this size.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_5MIN

DB_INDEX_NUM

Total number of indexes

Count

DB

This KPI displays information about the total number of indexes. An index is a copy of a database table that is reduced to certain fields. This copy is always in sorted form. Sorted data always has faster access from a database table, so we use an index for the table while reading the database records. This index also contains a pointer that refers to the actual database table so that it can access fields that are not contained in the index. There are two kinds of index for a database table: primary indexes and secondary indexes.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DB_SIZE

Total size of database

MB

DB

This KPI displays the total size of the database. The total database size contains all tables, indexes, LOBs, free space and anything else stored in the total data volume.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DB_TAB_SIZE

Total size of tables

MB

DB

This KPI displays the actual value for the size of all tables. The current table sizes are determined by a report and saved in a database table, which forms the history of the table sizes and table growth. For more information on table sizes, see the SAP Help topic Table Sizes.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DB_TRIGGER_CNT_INVALID

Number of invalid DB triggers

Number

DB

This KPI displays the total number of invalid database triggers on the system.

Remote system

System

Any server

/DVD/MON_CL_COL_DB_TRIGGERS

DEF_1HOUR

DB_TS_FREE

Free size of DB tablespaces

MB

DB

This KPI displays the sum of all free sizes of tablespaces on the database.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DB_TS_USED_P

Used size of database tablespaces

%

DB

This KPI displays the percentage for the used size of all tablespaces on the database. 

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DB_USED_P

Used space on database

%

DB

This KPI displays the percentage of used space on the database.

Remote system

System

Any server

/DVD/MON_CL_COL_DB

DEF_1DAY

DEQ_ERROR_DLT

Number of errors that occurred when releasing locks since last run

Count

SAPSYS

The database system automatically sets database locks when it receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program. Database locks are physical locks on the database entries that are affected by these statements. You can only set a lock for an existing database entry because the lock mechanism uses a lock flag in the entry. These flags are automatically deleted during each database commit. Database locks are therefore never available longer than for one database LUW only. As a result, in ABAP application programming, database locks cannot exist for longer than the duration of one dialog step. If there are errors when releasing these locks, this KPI counts the number of these errors since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

DISK_AVG_WAIT

Average disk wait (server)

ms

OS

This KPI displays the average disk wait on the server.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

DISK_RESPONS_SYS

Average disk response time (all servers)

ms

OS

This KPI displays average disk response time on all servers.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

DISK_UTIL_SYS

Average disk utilization (all servers)

%

OS

This KPI displays the disk utilization on all servers.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

DUMP_ALL_WITH_DETAILS

Number of new ABAP runtime errors (DUMPs)

Count

SAPSYS

This KPI displays the number of new ABAP runtime errors that have occurred since the last run of the collector job. 

Remote system

System

Any server

/DVD/MON_CL_COL_GET_DUMP

DEF_1DAY

DUMP_DBIF

Number of ABAP runtime errors (DUMPs) for SQL operations

Count

SAPSYS

This KPI displays the number of ABAP runtime errors that occurred due to a failed SQL operation and error ID starting with DBIF*. This value is counted from the last monitoring snapshot.
By default, all runtime errors are counted from all system clients. If you want to count only runtime errors that occurred on the current client, you must set the collector parameter COLLECT_FROM_ALL_CLIENTS to the value <empty>.

Remote system

System

Any server

/DVD/MON_CL_COL_GET_DUMP

DEF_1HOUR

DUMP_NBR_SUM

Number of ABAP runtime errors (DUMPs) (all servers)

Count

SAPSYS

This KPI displays the number of ABAP runtime errors that have occurred on all servers since the last run of the collector job.

Central system

System

Any server

/DVD/MON_CL_COL_GET_DUMP

DEF_1DAY

DUMP_SYNTAX_ERR

Number of ABAP runtime errors (DUMPs) with syntax error

Count

SAPSYS

This KPI displays the number of ABAP runtime errors that have occurred due to the syntax errors with following error IDs:

• DYNPRO_SYNTAX_ERROR

• SYNTAX_ERROR

By default, all runtime errors are counted from all system clients. If you want to count only runtime errors that occurred on the current client, you must set the collector parameter COLLECT_FROM_ALL_CLIENTS to the value <empty>.

Remote system

System

Any server

/DVD/MON_CL_COL_GET_DUMP

DEF_1HOUR

EMG_TOTAL

ABAP global extended memory total size (server)

MB

SAPSYS

The global extended memory (EG) is part of the extended memory (EM). It contains user-specific data and can be accessed by all work processes.

The EG is a part of the EM, which is used for multiprocessing. The EG contains data that does not belong to a specific user session. This may be data used for example for monitoring and statistics, or table buffers of the database interface (DBI),or ABAP shared objects that all work processes have access to independently of the user session. This KPI shows the total size of the global extended memory.

Remote system

Server

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

EMG_USED_P

ABAP global extended memory usage (server)

%

SAPSYS

The global extended memory (EG) is part of the extended memory (EM). It contains user-specific data and can be accessed by all work processes.

The EG is a part of the EM, which is used for multiprocessing. The EG contains data that does not belong to a specific user session. This may be data used for example for monitoring and statistics, or table buffers of the database interface (DBI),or ABAP shared objects that all work processes have access to independently of the user session. This KPI shows the total size of the extended global memory currently used (during the collector run) in percent.

Remote system

Server

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

Remote system

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

EM_USED_P

ABAP extended memory usage (server)

%

SAPSYS

This KPI displays the maximum amount of extended memory used on all servers. The extended memory (EM) contains data associated with work processes, such as variables, lists, and internal tables.

Remote system

Server

Only application server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

ENQ_ARG_MAX_CNT

Maximum number of different lock arguments in the lock table

Count

SAPSYS

This KPI displays the maximum number of possible or allowed lock arguments. The lock argument of a table in the lock object consists of the key fields of the table. The lock argument fields of a lock object are used as input parameters in the function modules for setting and removing locks that are generated from the lock object definition. When these function modules are called, the table rows to be locked or unlocked are specified by defining certain values in these fields. These values can also be generic. The lock argument fields define which subset of the table rows must be locked.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_ARG_NOW_LVL

Current number of different lock arguments stored in the lock table

Count

SAPSYS

This KPI displays the total number of different lock arguments stored in this lock table. The lock argument of a table in the lock object consists of the key fields of the table. The lock argument fields of a lock object are used as input parameters in the function modules for setting and removing locks that are generated from the lock object definition. The lock table is a table in the main memory of the enqueue server that records the current locks in the system. For each elementary lock, the table specifies the owner, the lock mode, the name and the fields in the locked table. The lock table is used to manage locks. Every time the enqueue server receives a lock request, the system checks the lock table to determine whether the request collides with an existing lock. If this is the case, the request is rejected. Otherwise, the new lock is written to the lock table.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_CLEAN_REQ_DLT

Number of releases for all locks of an application server since the last run

Count

SAPSYS

This KPI calculates the number of all releases of all locks of a selected application server since the last run. Physical lock mechanisms in the database system are insufficient for the requirements of an ABAP transaction. The locks must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and even different application servers.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_ENTR_MAX_CNT

Maximum number of elementary locks in the lock table

Count

SAPSYS

This KPI displays the maximum number of elementary locks in the lock table. The lock table is a table in the main memory of the enqueue server that records the current locks in the system. For each elementary lock, the table specifies the owner, the lock mode, the name and the fields in the locked table.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_ENTR_NOW_LVL

Current number of elementary locks in the lock table

Count

SAPSYS

This KPI displays the current number of elementary locks stored in the lock table. The lock table is a table in the main memory of the enqueue server that records the current locks in the system. For each elementary lock, the table specifies the owner, the lock mode, the name and the fields in the locked table.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_ERROR_DLT

Number of errors that occurred during lock requests since the last run

Count

SAPSYS

This KPI calculates the number of errors that occurred during lock requests since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_FILE_WRT_BCK_DLT

Number of write accesses to backup file since the last run

Count

SAPSYS

This KPI calculates the number of write accesses to the backup file since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_OWN_MAX_LVL

Highest number of lock owners in the lock table

Count

SAPSYS

This KPI calculates the highest number of lock owners in the lock table. A lock owner is a person who holds a lock. A lock can have one or two owners.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_REPORT_REQ_DLT

Number of operations for reading the lock table since the last run

Count

SAPSYS

This KPI calculates the number of operations for reading the lock table since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_REQUEST_CNTD

Number of lock requests per minute since the last run

*/min

SAPSYS

This KPI calculates the delta between the value of ENQ processed at the last snapshot and the current value, divided by the number of minutes since the last snapshot. The output is the number of ENQ processed per minute. If there is a high number of work processes in SAPLSENA and the number of ENQ per minute is high, the issue is that the application is raising too many ENQ. The solution is to find the root cause of this high number of ENQ, e.g. too many small packets or too many requests in rsiccont. It is useful to monitor the number of parallel processes.

Central system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_REQ_REJ_CNTD

Number of rejected lock requests per minute since the last run

*/min

SAPSYS

This KPI calculates the number of rejected lock requests per minute since the last run.

Central system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_AVG_NUM_SEARCH

Average number in search result

Number

SAPSYS

This KPI shows the average number of locks returned by all read operations.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_AVG_NUM_UPDATE

Average number in update replica

Number

SAPSYS

This KPI shows the average number of locks transferred by all update replica operations.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

Any server

DEF_5MIN

ENQ_SER2_DATA_RECEIVED_DLT

Received data since the last run

MB

SAPSYS

This KPI shows the total number of MBs received from Standalone Enqueue Server 2 clients since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_ERRORS_CONN_DLT

Number of connection errors since the last run

Number

SAPSYS

This KPI shows the number of connection errors that occurred on the Standalone Enqueue Server 2 (for example due to traffic control) since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_LOCKS_CONFIG

Configured number of locks

Number

SAPSYS

This KPI shows the highest possible number of lock entries that can occur in the lock table at the same time. Cumulative counters are not included.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_LOCKS_PEAK

Peak number of locks

Number

SAPSYS

This KPI shows the highest number of lock entries that occurred in the lock table at the same time. Cumulative counters are not included.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_LOCK_COLLISIONS_DLT

Number of lock collisions

Number

SAPSYS

This KPI shows the number of all enqueue operations rejected because the requested lock was already set by another process since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_MAX_NUM_TAKEOVER

Maximum number in takeover replica

Number

SAPSYS

This KPI shows the highest number of locks transferred by a single takeover replica operation.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_NETWORK_REQ_DLT

Number of network requests since the last run

Number

SAPSYS

This KPI shows the number of network requests since the last run. A network request may include several lock operation requests.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_BACKUP_DLT

Number of backup operations since the last run

Number

SAPSYS

This KPI shows the number of operations that have written locks to the backup file since the last run. Backed up locks are copied to the lock table after a restart of the enqueue server.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_ENQUEUE_DLT

Number of enqueue operations since the last run

Number

SAPSYS

This KPI shows the number of operations that have set or tried to set a lock since the last run. This number includes the increase of the cumulative counter of one lock table entry as well.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_REMOVE_DLT

Number of remove operations since the last run

Number

SAPSYS

This KPI shows the number of operations that have removed specific locks in the lock table since the last run. The lock entry is removed from the lock table regardless of the value of the cumulative counter.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_REM_OWN_PATT_DLT

Number of remove owner pattern operations since last run

Number

SAPSYS

This KPI shows the number of operations that have removed locks matching a specified owner pattern since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_REPL_TAKEOVER_DLT

Number of takeover replica operations since the last run

Number

SAPSYS

This KPI shows the number of operations that have taken over the replication table as new lock table since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OP_TOTAL_DLT

Total number of lock operations since the last run

Number

SAPSYS

This KPI shows the total number of operations that access the lock table:

• Enqueue operations

• Dequeue operations

• Dequeue all operations

• Read operations

• Backup operations

• Remove operations

• Remove owner pattern operations

• Remove argument pattern operations

Administrative operations are not included.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_OVERFLOWS_SESSION_DLT

Number of session overflows since the last run

Number

SAPSYS

This KPI shows the number of session overflows since the last run. One single ABAP session should not be able to overflow the lock table by setting too many locks. Therefore, a session quota is implemented that can be configured to a specific value, for example 20%.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_ROLL_IN_DLT

Number of roll-ins of connection since the last run

Number

SAPSYS

This KPI shows number of times the watchdog thread has handed over the request processing back to a worker thread since the last run. A roll-in happens, for example, if a client sends the next request to the server after a specified time of inactivity.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_SER2_TIMEOUTS_DLT

Number of timeouts since the last run

Number

SAPSYS

This KPI shows the number of timeouts that have occurred on the server since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_TOTAL_TIME_DLT

Total time spent in the critical path for lock operations since the last run

sec

SAPSYS

This KPI calculates the total time spent in the critical path for lock operations since the last run.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_TOT_SER_TIME_DLT

Total time spent in the enqueue server since the last run

sec

SAPSYS

This KPI calculates the total time spent in the enqueue server since the last run. The enqueue server (also known as the lock server) is the SAP system component that manages the lock table. There is only one enqueue server in a distributed SAP system. The enqueue server receives a lock request and checks the lock table to determine whether the lock request collides with an existing lock. If it does, the enqueue server rejects it. If it does not collide, the enqueue server sets the lock and makes the entry in the lock table.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

ENQ_UPD_NOW_LVL

Current number of open update requests with locks

Count

SAPSYS

This KPI calculates the current number of outstanding update requests.

Remote system

System

Any server

/DVD/MON_CL_COL_ENQUEUE_STAT

DEF_5MIN

FBA_APPLOGSIZE

Application log size (total)

MB

SAPSYS

This KPI displays the total size of the following application log tables:

• BALC: Log or message context

• BALDAT: Log data

• BALHDR: Log header

• BALHDRP: Log parameter

• BALM: Log message

• BALMP: Message parameter

• BAL_INDX: INDX tables

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FBA_BATCHJOB

Batch job size (total)

MB

SAPSYS

This KPI displays the total size of the background job processing tables:

• TBTCO: Job status overview table

• TBTCP: Background job step overview

• TBTCR: Batch scheduler execution time

• TBTCS: Time schedule table

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FBA_DBTABLOGSIZE

Table log size (total)

MB

SAPSYS

This KPI displays total size of the table DBTABLOG – Log records of table changes.

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FBA_RFCLOGSIZE

RFC log size (total)

MB

SAPSYS

This KPI displays the total size of the following tables:

• ARFCRSTATE: Status of ARFC calls on receiver side

• ARFCSDATA: ARFC call data (callers)

• ARFCSSTATE: Description of ARFC call status (send)

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FBA_SPOOLREQSIZE

Spool request size (total)

MB

SAPSYS

This KPI displays the total size of the following tables:

• TSP01: Spool requests

• TST03: TemSe data

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FBA_UPDREQSIZE

Update request size (total)

MB

SAPSYS

This KPI displays the total size of the following tables:

• VBDATA: Update data

• VBHDR: Update header

• VBMOD: Update function modules

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_BASIS

FER_WF_ITEM_SIZE

Workflow item size (total)

MB

ERP

This KPI displays the total size of the following tables:

• SOFM: SAPoffice: Folder Contents

• SORD: SAPoffice: Viewed Records for Shared Folders

• SORS: SAPoffice: Resubmission of User

• SWFDEVINST: Event Linkages with Instance Reference

• SWFRCRLINST: Correlation Runtime: Instances

• SWFREXTPROC: Workflow: Relation Between Work Item and External Process

• SWP_HEADER: Workflow Instances: Header Data of a Workflow Execution

• SWP_JOIN: Workflow Instances: Join Node of a Workflow Execution

• SWP_NODEWI: WF: Work Items for Nodes in a Workflow Definition

• SWP_SUSPEN: Workflow Instances: Suspended Work Item Callbacks

• SWPCMPCONT: Component Container of WFM

• SWPNODE: WFM: Node Properties and Node Hierarchy at Runtime

• SWPNODELOG: Workflow: Instance Data of Nodes of a Workflow Execution

• SWPSTEPLOG: Workflow: Instance Data of Steps of a Workflow Execution

• SWW_CONT: Workflow Runtime: Work Item Data Container

• SWW_CONTOB: Workflow Runtime: Work Item Data Container (Only Objects)

• SWW_EVENTS: Workflow: Events in Workflow

• SWW_WI2OBJ: Workflow Runtime: Relation of Work Item to Object

• SWWCNTP0: Workflow Container: XML Database (P0)

• SWWCNTPADD: Workflow Runtime: Persistence for Additional Container (XML)

• SWWEI: Workflow Runtime: Work Items of Type E (Event Items)

• SWWLOGHIST: Workflow Runtime: History of a Work Item

• SWWORGTASK: Workflow Runtime: Assignment of WIs to Org. Unit/Task

• SWWUSERWI: Current Work Items Assigned to a User

• SWWWIAGENT: Workflow Runtime: Agents for Execution of a Work Item

• SWWWIDEADL: Workflow Runtime: Deadline Data for Work Items

• SWWWIDH: Workflow Runtime: Deadline Monitoring of Work Items

• SWWWIHEAD: Workflow Runtime: Header Table for All Work Item Types

• SWWWIRET: Workflow Runtime: Return Values of Method Call

• SWZAI: Header Table for all Properties of a Work Queue

• SWZAIENTRY: Object Table for Work Queues (Entries)

• SWZAIRET: Return Values of Method Call of a WQ Line

Remote system

System

Any server

/DVD/MON_CL_COL_TAB

FS_ERP

GRC_AOC_BC_ALL

Number of SAP_BC roles with full authorizations at org. level

Count

GRC

This KPI displays the total number of SAP_BC roles that have full authorizations at the organization level.

Remote system

System

Any server

/DVD/MON_GRC_CL_COL_AUTH_OC

GRC_1DAY

GRC_AOC_ZCOM_ALL

Number of X, Y, Z* roles with full authorizations at org. level

Count

GRC

This KPI displays the total number of custom roles (starting with X, Y, Z*) that have full authorizations at the organization level.

Remote system

System

Any server

/DVD/MON_GRC_CL_COL_AUTH_OC

GRC_1DAY

GRC_AUTH_ALL_O_N

Number of NEW users with full authorizations (SAP_ALL, SAP_NEW)

Count

GRC

This KPI displays the number of new identified users since the last run of the collector execution, which have the full authorizations (SAP_ALL, SAP_NEW).

Remote system

System

Any server

/DVD/MON_GRC_CL_COL_USR_AUTH

GRC_1DAY

GRC_REF_USR_CNT

Number of used reference users

Count

GRC

This KPI displays the number of used reference users on the system.

Remote system

System

Any server

/DVD/MON_GRC_CL_COL_REF_USERS

GRC_1DAY

HEAP_DIA

ABAP Heap memory dialog quota (server)

MB

SAPSYS

This KPI displays the amount of heap memory (private memory) that an SAP dialog work process can allocate on an application server. The official parameter for this KPI is abap/heap_area_dia.

Remote system

Server

Only application server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_TOTAL

Heap memory available (server)

MB

SAPSYS

This KPI displays the total size of heap memory assigned to an application server. This value contains dialog and non-dialog heap memory sizes combined. The official parameter for this KPI is abap/heap_area_total.

Remote system

Server

Only application server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_USED_DIA

ABAP Heap memory dialog used size (server)

MB

SAPSYS

This KPI shows how much dialog heap memory is used in a specific time for an application server. Only dialog work processes can use this private memory.

Remote system

Server 

Only application server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_USED_DIA_P_SYS_MAX

ABAP Heap memory dialog usage max. (all servers)

%

SAPSYS

This KPI shows how much dialog heap memory is used across all application servers as a percentage.

Central system

System

Any server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_USED_NONDIA_P

ABAP Heap memory non-dialog usage (server)

%

SAPSYS

This KPI shows how much non-dialog heap memory is used in a specific time for an application server as a percentage. Only non-dialog work processes can use this private memory.

Remote system

Server 

Only application server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_USED_TOTAL

ABAP Heap memory used (server)

MB

SAPSYS

This KPI displays the total size of the allocated heap memory in a specific time for an application server. It defines how much total heap is used by dialog and non-dialog work processes combined.

Remote system

Server

Only application server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

HEAP_USED_TOTAL_P_SYS_MAX

ABAP Heap memory usage max. (all servers)

%

SAPSYS

This KPI shows how much heap memory (dialog and non-dialog) is used in total across all application servers as a percentage.

Central system

System

Any server

/DVD/MON_CL_COL_HEAP

DEF_5MIN

ICM_CURR_QUE

Number of current entries in queue (server)

Count

SAPSYS

This KPI shows how many entries are currently in the request queue.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_IDLE_THR

Number of idle threads (server)

Count

SAPSYS

This KPI displays the number of threads on an application server that have the status Idle.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_MAX_QUE

Maximum limit for allowed entries in request queue (server)

Count

SAPSYS

This KPI displays the maximum number of entries that are allowed in a request queue at the same time.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_PEAK_CONN

All-time peak connections (server)

Count

SAPSYS

This KPI displays the all-time peak number of connections identified on an application server at one time. The specific time used is the time when the monitoring was executed and the data was collected.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_PEAK_THR

All-time peak threads (server)

Count

SAPSYS

This KPI displays the all-time peak number of threads that were active at the same time.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_RUN_THR_P

Percentage of used running threads (server)

%

SAPSYS

This KPI shows how many threads are being used and therefore have the status Running at a specific point in time (running threads divided by all threads). If this value is 20%, for example, the remaining 80% are threads with the status Idle or occasionally with the status Unknown if SAP cannot determine the status.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_USED_CONN_P

Percentage of used connections (server)

%

SAPSYS

This KPI displays the percentage of used connections (current connections/max. allowed connections). An application server can have a large amount of connections allowed and only few of them used. Values below 1% usage are reported as 0%.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

ICM_USED_THR_P

Percentage of used available threads (server)

%

SAPSYS

This KPI displays the percentage of threads that are available at one time compared to the maximum number of allowed threads on an application server.

Remote system

Server

Only application server

/DVD/MON_CL_COL_ICM

DEF_5MIN

LAN_ERROR_IN_SYS_SUM

Total number of network errors: In (all servers)

Count

OS

This KPI displays the total number of network errors that occur for receiving packets per second on all servers. You can check this KPI via transaction ST06 by clicking Snapshot > LAN.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

LAN_ERROR_OUT_SYS_SUM

Total number of network errors: Out (all servers)

Count

OS

This KPI displays the total number of network errors that occur for sending packets per second on all servers. You can check this KPI via transaction ST06 by clicking Snapshot > LAN.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

LAN_PACKETS_IN_SYS_SUM

Total number of network packets: In (all servers)

Count

OS

This KPI displays the total number of network packets of type In on all servers.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

LAN_PACKETS_OUT_SYS_SUM

Total number of network packets: Out (all servers)

Count

OS

This KPI displays the total number of network packets of type Out on all servers.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

LOCK_NUM_ALL

Number of all existing lock entries

Number

SAPSYS

This KPI displays the total number of existing lock entries on the system.

Remote system

System

Any server

/DVD/MON_CL_COL_LOCKS

DEF_5MIN

LOCK_NUM_LONG_RUNNING

Number of lock entries exceeding the time limit

Number

SAPSYS

This KPI displays the number of lock entries for which the actual duration exceeds the configured time limit in minutes. By default, if you do not define any custom rules in the input table /DVD/MON_LOCK_I, a time limit of 10 minutes is automatically used.

Remote system

System

Any server

/DVD/MON_CL_COL_LOCKS

DEF_5MIN

LOCK_NUM_MODE_O

Number of optimistic locks (lock mode O)

Number

SAPSYS

This KPI displays the number of optimistic locks (Lock mode O) available in transaction SM12 based on the configured custom rules. By default, if you do not define any custom rules in the input table /DVD/MON_LOCK_I, all optimistic locks are counted toward this KPI value.

Remote system

System

Any server

/DVD/MON_CL_COL_LOCKS

DEF_5MIN

LOCK_NUM_MODE_X

Number of exclusive non-cumulative locks (lock mode X)

Number

SAPSYS

This KPI displays the number of exclusive, non-cumulative locks (Lock mode X) available in transaction SM12 based on the configured custom rules. By default, if you do not define any custom rules in the input table /DVD/MON_LOCK_I, all exclusive, non-cumulative locks are counted toward this KPI value.

Remote system

System

Any server

/DVD/MON_CL_COL_LOCKS

DEF_5MIN

DEF_5MIN

DEF_5MIN

MEM_FREE_SUM

Total free physical memory in system (all servers)

kB

OS

This KPI displays the total sum of free physical memory in the system on all servers in kB. It displays the total free memory for the whole system.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

MEM_PHYS

Physical memory available (server)

MB

OS

This KPI displays the physical memory that is available on the server.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

MEM_USED_P_SYS_MAX

Maximum physical memory used (all servers)

%

OS

This KPI displays the maximum physical memory used on all servers as a percentage.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

NR_MAX_DIFF

Maximum incremental difference of all number ranges

Count

SAPSYS

This KPI displays the maximum incremental difference found in a single monitored number range compared with all other number ranges.

Remote system

System

Any server

/DVD/MON_CL_COL_NUM_RANGE

DEF_1DAY

NR_OVER_THR

Number of number ranges that are over the threshold

Count

SAPSYS

This KPI displays the total number of number ranges that are over threshold. It considers all thresholds: speed, difference and percentage. You can view the default value for each threshold in the collector parameters.

Remote system

System

Any server

/DVD/MON_CL_COL_NUM_RANGE

DEF_1DAY

NR_TOTAL_SPEED

Sum of all speeds of monitored number ranges

Value/day

SAPSYS

This KPI displays the total speed of all monitored number ranges. This value represents how fast numbers are assigned to number ranges per day.

Remote system

System

Any server

/DVD/MON_CL_COL_NUM_RANGE

DEF_1DAY

PAGE_IN

Pages IN in kB/s

kB/s

OS

This KPI displays the value for Pages IN from the memory per hour.

Remote system

Server

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

PAGE_IN_P_SYS_MAX

Maximum percentage of Pages IN from memory per hour (all servers)

%

OS

This KPI displays the maximum percentage of Pages IN from the memory per hour from all servers. The memory utilization statistics are important to ensure that the system is running smoothly.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

PAGE_OUT_P

Pages OUT from memory per hour (server)

%

OS

This KPI displays the number of Pages OUT per hour. The memory utilization statistics are important to ensure that the system is running smoothly.

Central system

System

Any server

/DVD/MON_CL_COL_MEM_CPU_LAN

DEF_5MIN

PARAM_CHANGED

Number of changed system profile parameters

Count

SAPSYS

This KPI displays the number of changed profile parameters. You can change the parameters in transaction RZ11. Note that some changes can affect the security or performance of system. Additional details about changed parameters are available in the detail table Changed profile parameters (app. server).

Remote system

System

Any server

/DVD/MON_CL_COL_PARAM

DEF_1DAY

PG_CFG_SYS_MEM

ABAP Paging area: Max. size in shared memory (all servers)

MB

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is “rolled out” of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the maximum size of the paging area in the shared memory only among all servers. The disk is excluded.

Central system

System

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PG_CFG_TOTAL

ABAP Paging area: Size of the paging area (server)

MB

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is "rolled out" of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the total size of the paging memory. This includes the shared memory and the virtual memory on the disk.

Remote system

Server

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PG_PEAK

ABAP Paging area: Peak paging area used (server)

MB

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is “rolled out” of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the all-time peak usage of the paging memory.

Remote system

Server

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PG_SYS_PEAK_MAX

ABAP Paging area: Max. peak paging area used (all servers)

MB

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is “rolled out” of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the maximum peak usage of the paging memory among all servers.

Central system

System

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PG_SYS_USED_P_MAX

ABAP Paging area: Max. curr. used paging area (all servers)

%

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is “rolled out” of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the maximum currently used paging memory of all servers as a percentage.

Central system

System

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PG_USED_P

ABAP Paging area: Currently used paging area (server)

%

OS

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is “rolled out” of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program.

This KPI displays the currently used paging memory as a percentage (currently used / total size).

Remote system

Server

Any server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

PI_MSG_ERROR

Number of PI error messages

Count

SAPSYS

This KPI displays the number of failed PI messages (Exchange Infrastructure/Process Integration/Process Orchestration) collected from transaction SXI_MONITOR. PI messages provide details about the traffic flow that passes through a PI system. A value greater than zero means that there are issues in the traffic that passes through the PI system.

The detail table /DVD/MON_PI_D1 – PI status messages contains detail records for each collected failed PI message.
The numbers of PI messages that ended with an error status are as follows:

• 014: System error – manual restart possible

• 017: Application error – manual restart possible

• 018: System error – after automatic restart

• 022: Acknowledgment message stopped

• 023: System error – restart not possible

• 024: Application error – restart not possible

• 025: Application error – after automatic restart

• 114: System error (WS)

• 117: Application error (WS)

Remote system

System

Any server

/DVD/MON_PI_CL_COL_MSG

PI_5MIN

QRFC_ERR_OUT

Number of erroneous outbound qRFC queues

Number

SAPSYS

This KPI displays the number of erroneous outbound qRFC queues on all clients with the status SYSFAIL.

Remote system

System

Any server

/DVD/MON_CL_COL_QRFC

DEF_5MIN

QRFC_OUT

Number of all entries for outbound qRFC queues

Number

SAPSYS

This KPI displays the number of all entries from the table TRFCQOUT for outbound qRFC queues on all clients.

Remote system

System

Any server

/DVD/MON_CL_COL_QRFC

DEF_5MIN

QRFC_QOUT_COUNT

Number of outbound qRFC queues

Number

SAPSYS

This KPI displays the number of outbound qRFC queues on all clients.

Remote system

System

Any server

/DVD/MON_CL_COL_QRFC

DEF_5MIN

This KPI displays the number of read requests in the queue for batch (BTC) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of written requests in the queue for batch (BTC) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of read requests in the queue for dialog (DIA) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the queue for dialog (DIA) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of read requests in the queue for the dispatcher (DISP) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the queue for the dispatcher (DISP) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of read requests in the queue for SAP Gateway (GW) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of written requests in the queue for SAP Gateway (GW) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of read requests in the queue for the Internet Communication Manager (ICM) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the queue for the Internet Communication Manager (ICM) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of read requests in the local queues of work processes (LWP) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the local queues of work processes (LWP) on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of read requests in the queue for spool (SPO) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of written requests in the queue for spool (SPO) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of read requests in the queue for V2 update (UPD2) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the queue for V2 update (UPD2) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

SAPSYS

This KPI displays the number of read requests in the queue for update (UPD) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

This KPI displays the number of written requests in the queue for update (UPD) work processes on the application server since the last run of the collector execution and reflects the metrics from transaction SM51 (Information > Queue Information). The queue is considered to be healthy when the number of read requests equals the number of written requests for the same request type.

The dispatcher forwards each request it receives to a work process of the appropriate type. If all the processes of this type are occupied, the dispatcher stores the request in a queue.

Only application server

RFC_CIF_OUT_15

TRFCQOUT: Number of CIF queue entries older than 15 minutes

Count

SAPSYS

This KPI displays the number of CIF queue entries in the table TRFCQOUT that are older than 15 minutes. During the transfer of data between two SAP systems, errors can occur that lead to faulty queue entries. Faulty queue entries must be rectified as soon as possible before they lead to serialization effects. To do so, you must be able to display the contents of the queues in such a way that you can identify the object which caused the error as quickly as possible and make any necessary changes. The CIF queue display enables you to do this.

TRFCQOUT is a standard SAP table that is used to store tRFC queue description (outbound queue) information. The relevant SAP transactions for viewing this information are SE11 or SE16.

Remote system

System

Any server

/DVD/MON_CL_COL_RFCQ

DEF_1HOUR

RFC_IN_CON_ERR

Number of failed RFC tests – RFC check without authorization

Count

SAPSYS

This KPI displays the number of failed connection tests. A connection test checks if the requested SAP system is available and running. A value greater than zero indicates a problem. Check the detail table /DVD/MON_S_RFC_DETAILS – Details for unsuccessful RFC connection tests, which contains the list of failed RFC destinations.

Remote system

System

Any server

/DVD/MON_CL_COL_RFC

DEF_1HOUR

RFC_LOCK_ALL

Number of all cross-system RFC locks

Count

SAPSYS

This KPI displays all cross-system RFC locks collected for the last N day(s). The default value is 1 day. If needed, you can adjust the value N with the collector parameter RFC_LOCK_DAYS_BACK_THRESHOLD.

Collected data is extracted in the same way as in transaction SMCL. In addition, RFC locks are selected based on the defined criteria in the input table /DVD/MON_LCK_RFC. This input table reflects the select options used in transaction SMCL. If no records are defined in this input table, the remote token manager system is selected with the function module CSLTM_GETTOKENMANAGER by default, and all existing RFC locks that are no older than N day(s) are reported.

Remote system

System

Any server

/DVD/MON_CL_COL_RFC_LOCKS

DEF_1DAY

ROLL_USED_P

ABAP Roll area used size (server)

%

OS

This KPI displays the amount of roll area that is used. Context data is stored in the roll area, such as user authorizations, set or get parameters, pointers to active programs, and defaults. The remaining portion of the roll area is used when the system can no longer allocate extended memory, either because the extended memory is full or because the quota has been reached.

Remote system

Server

Only application server

/DVD/MON_CL_COL_BUFF

DEF_5MIN

SDTR_ERROR_CNT

Number of erroneous transmissions

Count

SAPSYS

This KPI displays the total number of transmission records that have the status Error.

Remote system

System

Any server

/DVD/MON_CL_COL_SEND_TRANSMIT

DEF_1HOUR

SDTR_WAITING_CNT

Number of waiting transmissions

Count

SAPSYS

This KPI displays the total number of transmission records that have the status Waiting. This includes records that are waiting, inconsistent or will be processed in the future.

Remote system

System

Any server

/DVD/MON_CL_COL_SEND_TRANSMIT

DEF_1HOUR

SERVER_IS_DOWN_SYS_SUM

System: Number of non-reachable servers

Number

OS

This KPI displays the total number of all non-reachable servers for the system (RFC and OS ping fails).

Central system

System

Any server

/DVD/MON_CL_COL_SYSTEM

DEF_1MIN

SERVER_RFC_FAIL

System: Server is unreachable via RFC (true = 1 / false = 0)

Boolean

OS

This KPI is similar to the KPI SERVER_IS_DOWN but more sensitive. The value 1 means that the server cannot be reached and is returned if the RFC ping fails. An OS ping is not used in this KPI. The value 0 corresponds to a successful RFC ping. This KPI does not have a collector assigned.

Central system

Server

Any server

/DVD/MON_CL_COL_SYSTEM

DEF_1MIN

SLG_DEBUG

Number of changes in debug mode

Count

SAPSYS

This KPI displays the number of changes in debug mode since the last collector job execution. It calculates the number of actions when a user jumps to debug mode in any application (either run in background or called via HTTP) and makes any changes directly in debug mode. For example, a user might change a value or program flow logic in debug mode. Such user actions are then recorded in system logs that form the basis for calculating this KPI. For more information about this KPI, see the collector detail table System log info.

Remote system

System

Any server

/DVD/MON_CL_COL_SYSLOG

DEF_1HOUR

SLG_PRIO_HIGH

Number of HIGH priority messages in the system log

Count

SAPSYS

This KPI displays the number of messages with the priority HIGH in the system logs.

Remote system

System

Any server

/DVD/MON_CL_COL_SYSLOG

DEF_1HOUR

SLG_PRIO_VERY_HIGH

Number of VERY HIGH priority messages in the system log

Count

SAPSYS

This KPI displays the number of messages with the priority VERY HIGH in the system logs.

Remote system

System

Any server

/DVD/MON_CL_COL_SYSLOG

DEF_1HOUR

SLT_REPLICATION_ALL_CNT

Total number of tables set for the replication

Count

SAPSYS

This KPI displays the total number of tables that are in the currently activated replication.

These SLT KPIs provide SAP Landscape Transformation replication monitoring. They monitor the current status of tables during the replication. By default, no monitoring takes place if the corresponding input table is empty. To enable SLT monitoring, maintain the input table /DVD/MON_SLT_I by defining which queues (mass transfer IDs) and which tables to monitor. The fields in the input table reflect the selection options in transaction LTRC.

Remote system

System

Any server

/DVD/MON_CL_COL_SLT

DEF_1HOUR

SLT_REPLICATION_INIT_CNT

Number of tables in the initial (load) replication phase

Count