(DI-2205) Complete List of Default KPIs
This is a complete list of delivered default KPIs:
| KPI name | Description | Unit | Monitoring area | Long description | Collected on | Collected for | Server specification | Collector | Profile | Recommended period |
|---|---|---|---|---|---|---|---|---|---|---|
| APP_LOGS | Number of application logs specified by rules | count | SAPSYS | This KPI represents a template definition which can be used to calculate the number of application logs. To start the monitoring of this KPI, you need to assign this KPI to the monitoring profile and into the input table '/DVD/MON_ALOG_I2'. In this input table you might define various settings based on which the specific application logs will be included to this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_APPLOG | N/A - need to schedule this KPI manually* | Custom |
| APP_LOGS_VERY_IMPORTANT | Number of VERY IMPORTANT application logs | count | SAPSYS | This KPI counts number of all application logs which were marked as very important by application. The list of the counted application logs can be found in the details for the KPI. Application log can be displayed via standard SAP transaction SLG1. | Remote system | System | any server | /DVD/MON_CL_COL_APPLOG | DEF_5MIN | 5 Minutes |
| ARFC_FREE | Number of available (free) WP for aRFC resources | count | SAPSYS | Calculates resources of an application server. Collects the number of available work processes for asynchronous RFC resources. For more information please check: 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 | 5 Minutes |
| ARFC_FREE_P | Percentage of available (free) WP for aRFC resources | % | SAPSYS | Calculates resources of an application server. Collects percentage of available work processes for asynchronous RFC resources. For more information please check: 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 | 5 Minutes |
| ARFC_FREE_P_MIN | Minimum of percentage of available WP for aRFC | % | SAPSYS | Each application server has configured number of WP used for asynchronous RFC. This KPI represent minimal percentage value of free WP from all application servers. | Central system | System | any server | /DVD/MON_CL_COL_ARFC | DEF_5MIN | 5 Minutes |
| ARFC_FREE_SUM | Number of available WP for aRFC resources (all servers) | count | SAPSYS | This KPI represents the number of all available work processes from all servers. | Central system | System | any server | /DVD/MON_CL_COL_ARFC | DEF_5MIN | 5 Minutes |
| BAT_DB_INSERT_AG | Average DB insert | ms | BENCH | This KPI shows the database insert time of the benchmark as average of collected values for this KPI in 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 (by default, N is 10 000 entries). If needed, this value can be changed 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 | 5 Minutes |
| BAT_DB_INSERT_MS | DB Insertion benchmark | ms | BENCH | This KPI shows the actual database insert time of the benchmark. 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 (by default, N is 10 000 entries). If needed, this value can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. | Central system | System | any server | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 Minutes |
| BAT_DB_SELECT_AG | Average DB select | ms | BENCH | This KPI shows the database select time of the benchmark as average of collected values for this KPI in 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 is using a WHERE clause on primary key, such as to select all N entries (N is by default 10 000 entries). If needed, this value can be changed 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 | 5 Minutes |
| BAT_DB_SELECT_MS | DB Select benchmark | ms | BENCH | This KPI shows the actual database select time of the benchmark. 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 is using a WHERE clause on primary key, such as to select all N entries (N is by default 10 000 entries). If needed, this value can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. Database select and its average is measured by the KPI with name BAT_DB_SELECT_AG. | Central system | System | any server | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 Minutes |
| BAT_DB_UPDATE_AG | Average DB update | ms | BENCH | This KPI shows the database update time of the benchmark as average of collected values for this KPI in 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 are occurring with WHERE clause on primary key, such as to update single non-key field on N entries (N is by default 10 000 entries). If needed, this value can be changed 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 | 5 Minutes |
| BAT_DB_UPDATE_MS | DB Update benchmark | ms | BENCH | This KPI shows the actual database update time of the benchmark. 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 are occurring with WHERE clause on primary key, such as to update single non-key field on N entries (N is by default 10 000 entries). If needed, this value can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. | Central system | System | any server | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 Minutes |
| BTC_NUM_DELAYED | Number of delayed background jobs ( >= 60 seconds) | count | SAPSYS | This KPI value represents a number of background jobs that waiting for free work process more then 60 seconds. | Remote system | System | any server | /DVD/MON_CL_COL_BG_JOBS | DEF_5MIN | 5 Minutes |
| BTC_NUM_FAILED | Number of failed background jobs | count | SAPSYS | This KPI value represents a number of background jobs that failed. | Remote system | System | any server | /DVD/MON_CL_COL_BG_JOBS | DEF_5MIN | 5 Minutes |
| BTC_NUM_LONGRUN | Number of background jobs running too long ( >= 10 minutes) | count | SAPSYS | This KPI value represents a number of background jobs that running more than 10 minutes. | Remote system | System | any server | /DVD/MON_CL_COL_BG_JOBS | DEF_5MIN | 5 Minutes |
| BWA_AGE_NEWSID | BWA: Age of oldest SID not processed | count | BWA | If master data SIDs are not updated in BWA, entries will remain in table RSDDTREXNEWSID. Table /DVD/MON_NEWSID contains the oldest SID and timestamp of RSDDTREXNEWSID. This KPI is the age of the oldest SID not updated in BWA. Check if attribute change run has failed or long running. Check bwa alerts for Master data index has been corrupted. Check Job BI_BIA_NEWMD_INDEX. Check application log: transaction SLG1, Filter: Object = RSDDTREX, Sub-object = TAGGRFILL. Check that object is still active (table RSDDBOBJDIR or transaction RSDDB). | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWASID | BWA_1HOUR | 1 Hour |
| BWA_ALERT_RED_NO | BWA: Number of red alerts | count | BWA | This is a count of number of red alerts in TREXADMIN. The details of the alert can be seen in "Details" tab with in a detail table "BWA Alerts". | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 Hour |
| BWA_CPU_USED | BWA: CPU load on most loaded blade | % | BWA | This KPI is the maximum CPU load (of all blades) calculated by TREXADMIN (function module TREX_EXT_LOAD_HISTORY) since the last execution of the collector. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_INDX_INA_DUR | BWA: Missing or inactive bwa cube index - duration | min | BWA | This KPI displays the maximum missing period in minutes for all cubes. When a cube index is created, the list of index that have been active once (table /DVD/MON_BWAINDX) is automatically updated on the satellite system at the next run of the agent. At each execution of the agent, Insights checks that all indexes exist and have status ACT. If an index is missing, Insights flags the index as missing, calculate since when it is missing and update the list that is visible in the detail table "BWA inactive indexes". | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 Hour |
| BWA_INDX_INA_NO | BWA: Number of missing or inactive BWA cube index | count | BWA | When a new BWA cube index is created, it is added automatically in table /DVD/MON_BWAINDX. An index can be missing for some time (example cube index is dropped and recreated after selective deletion),but if they are missing for too long, we want to be alerted. At each execution of the collector we check that all indexes contained in table /DVD/MON_BWAINDX have status ACT. This KPI counts the number of index missing for more than an authorized period value. The authorized period value can be maintain for each cube in /DVD/MON_BWAINDX, by default it is 90 minutes .If an index is deleted and will not be rebuild, it should be removed from /DVD/MON_BWAINDX to avoid the alert. The list of missing index is visible from tab "Details", BWA inactive indexes, column alert contains value "X", if the index has been missing for more than the authorized period value. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 Hour |
| BWA_IS_PING | BWA: IS Ping time | sec | BWA | This KPI displays the ping time in seconds calculated by TREXADMIN (function module TREX_EXT_LOAD_HISTORY) with a field IS_PING_TIME (ping time between the nameserver and the indexserver). The nameserver contacts each indexserver to check if the connection works fine. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_SERVICE_INAC | BWA: Number of inactive services | count | BWA | At each execution of the agent, we check the status of each service reported by TREXADMIN. This KPI counts the number of services where the status is not green. Sometimes the status is undefined (not green, not red), but it is visible only from time to time, so if Insights reports that some services are inactive, filter status on active NE green and refresh regularly to see the status on TREX. You can also see the service reported as inactive in the detail table "BWA service restarted or inactive". | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_SERVICE_REST | BWA: Number of restarted services | count | BWA | This KPI displays the number of service restarted since the last execution of the collector. At each execution of the agent we check the Start time of each service in TREXADMIN. When the memory consumption of a blade exceed the limit, the blade might restart by itself. When a blade restart all jobs and queries are killed so it has a major impact on users. With this indicator you can be alerted if a blade/service restarts to find the root cause of the restart. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_THRD_NO | BWA: Number of running threads for more than 10sec | count | BWA | If a blade is overloaded, the threads can slow down and number of long running threads will increase. This indicator can help you to detect when a blade is slowing down. Be aware that during the cube indexing or index merging, it is normal to have long running threads. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_THRD_TIME | BWA: Runtime of the longest thread | sec | BWA | This KPI displays the runtime of the longest running thread captured in TREXADMIN. This KPI can inform when there is a lock (zombie thread). If it does not cause any lock, an OSS message should be open to investigate further. If rollup, change run or master data SID update is locked and must be solved immediately, then a restart of index server and RFC server is required. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 Hour |
| BWA_TTLMEM | BWA: Percentage of memory on the most loaded blade | % | BWA | This KPI displays the maximum memory used of all blades calculated by TREXADMIN (function module TREX_EXT_LOAD_HISTORY) since the last execution of the collector. The speed of a BWA system is limited by the speed of the slowest blade. If you have 15 blades, it is important that you have memory available on all the blades. Instead of recording individually the memory of each blade, we can record only a KPI for the worth performing blade. The memory of blade 1,2 and 3 are recorded as benchmark. The details of all the blades are saved in detail table "BWA load". | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_TTLMEM_BL01 | BWA: Memory size on Blade 1 | MB | BWA | The most important KPI for memory is BWA_TTLMEM (BWA: Percentage of memory on the most loaded blade). As it is the most loaded blade, it will show different blade at different time. To see the trend on one blade, this KPIs for memory on blade 1, 2 and 3 are delivered. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_TTLMEM_BL02 | BWA: Memory size on Blade 2 | MB | BWA | The most important KPI for memory is BWA_TTLMEM (BWA: Percentage of memory on the most loaded blade). As it is the most loaded blade, it will show different blade at different time. To see the trend on one blade, this KPIs for memory on blade 1, 2 and 3 are delivered. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_TTLMEM_BL03 | BWA: Memory size on Blade 3 | MB | BWA | The most important KPI for memory is BWA_TTLMEM (BWA: Percentage of memory on the most loaded blade). As it is the most loaded blade, it will show different blade at different time. To see the trend on one blade, this KPIs for memory on blade 1, 2 and 3 are delivered. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 Minutes |
| BWA_UNLOADS | BWA: Number of Unloads (max per blade) | count | BWA | This is the highest unload per blade reported by TREXADMIN (function module TREX_EXT_LOAD_HISTORY) in the last 5 minutes. | Remote system | System | any server | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 Hour |
| BW_12503CNT | Javastack: Number of OLAP stats with event '12503' | count | JAVAST | This KPI calculates the number of OLAP Statistics with the event number '12503' in table RSDDSTAT_OLAP. Event number '12503' represents a successful end of the web template. When a web template v7 starts, it creates first an entry for event number '12502' in table RSDDSTAT_OLAP. At the successful end of the web template, a new entry with event number '12503' is created. If this template fails on java stack, in table RSDDSTAT_OLAD is available only entry for an event number '12502' (entry with event number '12503' is not available). | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CNT_NOTA | Javastack: Number of '12503' events on not authorized node | count | JAVAST | This KPI calculates the number events with number '12503' which occurred on not authorized node. Event number '12503' represents a successful end of the web template. When a web template v7 starts, it creates first an entry for event number '12502' in table RSDDSTAT_OLAP. At the successful end of the web template, a new entry with event number '12503' is created. If this template fails on java stack, in table RSDDSTAT_OLAD is available only entry for an event number '12502' (entry with event number '12503' is not available). | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CXMN_AVG | Javastack: Average number of '12503' events per each node | count | JAVAST | This KPI calculates the average number of events with number '12503' in the last X minutes (by default 60 minutes) per each node. This X value can be adjusted with the collector's parameter 'JAVASTACK_COUNT_12503_X_MINUTES'. | Central system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CXMN_MAX | Javastack: Maximum number of '12503' events per each node | count | JAVAST | This KPI calculates the maximum number of events with number '12503' in the last X minutes (by default 60 minutes) per each node. This X value can be adjusted with the collector's parameter 'JAVASTACK_COUNT_12503_X_MINUTES'. | Central system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CXMN_MIN | Javastack: Minimum number of '12503' events per each node | count | JAVAST | This KPI calculates the minimum number of events with number '12503' in the last X minutes (by default 60 minutes) per each node. This X value can be adjusted with the collector's parameter 'JAVASTACK_COUNT_12503_X_MINUTES'. | Central system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CXMN_MNV | Javastack: Minimum variance of '12503' events per each node | count | JAVAST | This KPI calculates the minimum variance for events with number '12503' in the last X minutes (by default 60 minutes) per each node. This X value can be adjusted with the collector's parameter 'JAVASTACK_COUNT_12503_X_MINUTES'. | Central system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503CXMN_MXV | Javastack: Maximum variance of '12503' events per each node | count | JAVAST | This KPI calculates the maximum variance for events with number '12503' in the last X minutes (by default 60 minutes) per each node. This X value can be adjusted with the collector's parameter 'JAVASTACK_COUNT_12503_X_MINUTES'. | Central system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503HEAPMAX | Javastack: Maximum number of heap for all nodes | count | JAVAST | This KPI displays the maximum number of heap from all nodes. For example, if there are 10 nodes for the BW system, instead of capturing and storing the memory of each node, the collector captures the memory of the most loaded. If the value remains at 84%, the memory consumption is too high. | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12503MISSUSR | Javastack: No. of users with 12502 without 12503 after X min | count | JAVAST | This KPI calculates the number, how many users have sessions with event number '12502', but not followed by event number '12503' after X minutes (by default 5 minutes). This means that web template has failed. There is a timeout after 15 minutes, so java stack session cannot take more than 15 minutes. However a java stack session should take only few seconds to 1 minute as it is a user tool (not batch processing). For monitoring of all KPIs on java stack, we need at least BW730SP8 and BI JAVA SP7 Patch 30. For more details, check the OSS note: <a href='Note'>https://service.sap.com/sap/support/notes/1069253'>Note 1069253 - BEx Web 7.x: Monitoring server node memory use in OLAP stats</a> | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12505NO | Javastack: Number of rejected queries (event 12505) | count | JAVAST | This KPI should be always zero. If there is an issue on memory of the java stack (for example, the GC stucks), this KPI will be greater than zero. When memory on java stack is above RSADMIN threshold, java stack will reject the request from the user (web template will not run) and create a new entry with event number '12505' in table RSDDSTAT_OLAP. | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_12640NO | Javastack: Number of cache refresh (event 12640) | count | JAVAST | This KPI displays the number of all cache refresh on java stack. Cache refresh is done when java stack is restarted or in exceptional cases, manually forced to refresh RSADMIN parameter. If no manual refresh is done, this KPI calculates all java stack restarts. | Remote system | System | any server | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 Minutes |
| BW_9000DMMISS | BW: Number of queries failing on DM (BWA, DB, HANA) | count | BW | When a queries fails on data manager (db2 or bwa),there is an entry in rsddstat_olap with event 9000 but no entries in rsddstat_dm. Queries can fail on db2 (eg dump signal 11) or on bwa (eg if all memory is used) or on HANA. The count shows how stable (or unstable) is db and bwa. A restart of bwa will make several queries to fail so will increase this value, like a reorg or a memory issue or a BWA index corrupted, or query above the safety belt of 40 million cells. No reaction expected if there is only 1 or 2 failures, but if many queries are failing at the same time it is a general issue that needs to be addresses and reoccurrence must be prevented. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| BW_AGGR_USAGE | BW: Aggregate usage | count | BW | Every 5 minutes we calculate the number of aggregate hit by comparing rsddstataggrdir field usage per aggregate with the previous snapshot. And table /DVD/MON_BWAGGRU is updated with the number of hit per aggregate per day. This is to find which aggregate are not used and can be deactivated to improve runtime of change run and rollup. | Remote system | System | any server | /DVD/MON_BW_CL_COL_AGGR_USAGE | BW_5MIN | 5 Minutes |
| BW_DURATTRIBCHAN | BW: Duration running attribute change run | s | BW | During change run, many BW jobs are locked so it is important that the attribute change run is not too long. This KPI calculates the Runtime of the currently running job BI_PROCESS_ATTRIBCHAN, BI_STRU* or BI_CHANGERUN_RESTART. The value of the KPI is calculated only for the running jobs and not the job finished; so the final actual runtime will be higher than the last value captured, but in the same range. If runtime is too long, administrators can be informed and can decide to drop aggregates if the adjust is too long running (e.g. job BICHNG), check runtime of activation of MD (BIACTI jobs) and create DB indexes if needed and check that the number of changes in IO is normal(same number of changes in source system and not increased by a bug or conflicting loads). | Remote system | System | any server | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 Minutes |
| BW_DURCOMPRESS | BW: Duration of the longest running cube compression | s | BW | This indicator shows the longest running cube compression, i.e. the longest running job BI_*COMP*.The value of the KPI is calculated only for the running jobs and not the job finished, so the final actual runtime will be higher than the last value captured, but in the same range. By calculating this value every few minutes, this allow to raise an alert if there is a long running cube compression and take ABAP, SQL traces to investigate the performance of this cube compression. | Remote system | System | any server | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 Minutes |
| BW_DURDBINDEX | BW: Duration of longest running DB indexing | s | BW | The SAP default is to drop indexes before the load and recreate the index after the load in the process chain. This is fine for full loads; but for delta, it can take hours to recreate the index. The time saved to load a small delta can be much lower than the time to rebuild. This indicators shows the longest running job BI_PROCESS_INDEX*.The value of the KPI is calculated only for the running jobs and not the job finished, so the final actual runtime will be higher than he last value captured, but in the same range. By calculating this value every few minutes, this allow to correlate those long running job and other issue on the system. If this is not required, this indicator can be deactivated and replaced by a daily check of the job BI_PROCESS_INDEX*. | Remote system | System | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 Minutes | |
| BW_DURLOADING | BW: Duration of longest running DTP | s | This indicators shows the longest running DTP (e.g. the longest running job BIDTPR_*).The value of the KPI is calculated only for the running jobs and not the job finished, so the final actual runtime will be higher than the last value captured, but in the same range. By calculating this value every few minutes, this allow to raise an alert if there is a long running DTP and take ABAP, SQL traces to investigate the performance of this DTP. | Remote system | System | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 Hour | ||
| BW_DURLOADIP | BW: Duration of longest running InfoPackage | s | BW | This indicators shows the longest running Info Package. From the enqueue of the running IP, we check the start time and calculate the delay between start time and current time. By calculating this value every few minutes, this allow to raise an alert if there is a long running Info Package and take ABAP, SQL traces to investigate the performance of this Info package. See table BW Info packages to see for the top N requests, the request number, number of packets, runtime, Info Package, Data source. Only Info packages with more than 50 packets or duration greater than 1800 seconds are recorded. Sometimes values are incorrect as no enqueue will be visible, this can lead to missing data but the trend should be always correct. | Remote system | System | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 Hour | |
| BW_DURMDACTIVAT | BW: Duration of the longest running MD activation | s | BW | This indicator shows the longest running Master Data activation job during change run, i.e. the longest running job BIACTI_*. The value of the KPI is calculated only for the running jobs and not the job finished, so the final actual runtime will be higher than the last value captured, but in the same range. By calculating this value every few minutes, this allow to raise an alert if there is a long running MD activation and take SQL traces to create the required index (usually CHANGED OBJVERS) on table P,Q,X,Y. | Remote system | System | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 Hour | |
| BW_DURODSACTIVAT | BW: Duration of the longest running ODS activation | s | BW | This indicators shows the longest running ODS (DSO) activation job, for the DSO where activation is done in batch and with at least 2 jobs in parallel (i.e. runtime of the running BIBCTL* jobs).The value of the KPI is calculated only for the running jobs and not the job finished; so the final actual runtime will be higher than the last value captured, but in the same range for the job BIBCTL that are slow. By calculating this value every few minutes, this allow to raise an alert if there is a long running DSO activation and take SQL traces to analyze the issue(can be system hanging due to backup hang, lock wait, network issue, missing DB index, missing DB stats). For packet size of 20.000 rows, normal runtime should be between 20 and 60sec. Everything above 500sec should be investigated. | Remote system | System | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 Hour | |
| BW_D_IP_ABTHRS | BW: Number of IP with more than X packets in previous day | count | BW | It is the number of request that was running yesterday (either started or finished yesterday) with more than 100 packets (100 is a parameter of the collector and can be changed).The detail can be seen in the detail tab, BW Daily stats on Info packages or in table /DVD/MON_BWDIP. The KPI is using following tables or could use in the future the following tables :RSMONICDP : RNR, cube, request, timestamp, rec_INSERT. index TSP on timestamp RSREQDONE RNR > ZPAK</BR>RSLDPIO -ZPAK > DataSource.... oltptyp = M master data, D transactional RSDDSTATWHM - RNR runtime RSMONFACT - not used as too large. Can be used in the future to calculate UR runtime of each packet</BR>RSMONMESS - take min timestamp from second line (first line is extraction time) = starttime and max = endtime per packet</BR>RSICCONT - targets per request. For the DTP, the following table could be used to enhance the KPI or a new KPI. RSBKREQUEST gives all DTP request (number of rows, time start, end) and DTP number RSBKDTP gives the details for the DTP (source and target)RSBKDATAPAKID for each packet of a DTP request, provides number of rows extracted, processed | Remote system | System | any server | /DVD/MON_BW_CL_COL_GET_D_IP | BW_1DAY | 1 Day |
| BW_ETL_EXCEEDED_PC | BW: Number of long running Process chains | number | BW | KPI value displays the total number of long-running Process chains. By default, if the Process chain is running more than 60 minutes, the collector considers this Process chain as long-running. Thresholds for long-running Process chains can be defined by Input table '/DVD/MON_BWPCINP'. | Remote system | System | any server | /DVD/MON_BW_CL_COL_ETL_PC | BW_1HOUR | 1 Hour |
| BW_ETL_FAILED_PC | BW: Number of failed Process chains | number | BW | KPI value displays the total number of failed Process chains since last run. | Remote system | System | any server | /DVD/MON_BW_CL_COL_ETL_PC | BW_1HOUR | 1 Hour |
| BW_ETL_FINISHED_PC | BW: Number of successfully finished Process chains | number | BW | KPI value displays the total number of successfully finished Process chains since last run. | Remote system | System | any server | /DVD/MON_BW_CL_COL_ETL_PC | BW_1HOUR | 1 Hour |
| BW_ETL_RUNNING_PC | BW: Number of running Process chains | number | BW | KPI value displays the total number of currently running Process chains. | Remote system | System | any server | /DVD/MON_BW_CL_COL_ETL_PC | BW_1HOUR | 1 Hour |
| BW_IP_MAX_PACKET | BW IP max number of packets (multiplied by number of target) | count | BW | Info Package loads spend too much on enqueues when the number of packets multiplied by the number of targets is more than 1000. We can have 500 packets and one target without performance issues, but if we have 500 packets and 10 targets, then most of the time will be spend on enqueue and not on processing the data. The number of packets not multiplied by the number of targets is not relevant and therefore not saved as a KPI. Below, when we refer to number of packets, it is always multiplied by the number of targets. This indicators shows the highest number of packets (multiplied by the number of targets) in the running Info Packages. From the enqueue of the running IP, we check the packet number that we can find in the monitor, and we multiply by the number of targets for this IP. If there are 2 IP running with more than 1000 small packets, there are so many ENQ processed that we have seen situation where system became very slow and rapidly 100% of the DIA WP were used. By calculating this value near real time, this allows to raise an alert and review the packet size (roosprms), number of rows in the IP. For full recovery loads, if the number of packets will be very high, it can be faster to kill the load and repeat with less packets. See tab ® details ¯ - ® BW Info packages ¯ to see for the top N requests, the request number, number of packets, the number of targets, number of packets multiplied by the number of targets, runtime, Info package, Info source, source, Data source. | Remote system | System | any server | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 Hour |
| BW_NR_MAX_DIFF | BW: Maximum from incremental difference of all number ranges | value | BW | This KPI presents the maximum counter increase of all BW number ranges. The detail table "Number range info" contains the list of the related number ranges with their consumption and buffer settings. | Remote system | System | any server | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 Day |
| BW_NR_MAX_SPEED | BW: Maximum from incremental speed of number ranges per day | val/d | BW | This KPI presents the maximum counter increase of all BW number ranges, calculated as daily increase. The detail table "Number range info" contains the list of the related number ranges with their consumption and buffer settings. | Remote system | System | any server | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 Day |
| BW_NR_OVER_THR | BW: Count of number range which are over threshold | count | BW | This KPI presents the count of BW number ranges, found over defined speed or difference threshold (by default, both thresholds are 0). If needed, these threshold values can be changed with the collector's parameters DIFFERENCE_THRESHOLD or SPEED_THRESHOLD. The detail table "Number range info" contains the list of the related number ranges with their consumption and buffer settings. | Remote system | System | any server | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 Day |
| BW_NR_TOTAL_DIFF | BW: Sum of all incremental differences from number ranges | value | BW | This KPI presents the total increase of all BW number ranges. The detail table "Number range info" contains the list of the related number ranges with their consumption and buffer settings. | Remote system | System | any server | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 Day |
| BW_NR_TOTAL_SPEE | BW: Incremental speed from all number ranges per day | val/d | BW | This KPI presents the total increase of all BW number ranges, calculated as daily increase. The detail table "Number range info" contains the list of the related number ranges with their consumption and buffer settings. | Remote system | System | any server | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 Day |
| BW_PC_STEP_COUNT | BW: Process Chain step count | count | BW | Number of steps that finished since the last execution of the agent. | Remote system | System | any server | /DVD/MON_BW_CL_COL_PC | BW_1HOUR | 1 Hour |
| BW_PC_STEP_ERR | BW: Process Chain step error | count | BW | Number of steps that finished in error since the last execution of the agent. If there are several steps in error in the last x minutes; it can show a general issue on the system(all BTC or DIA used, transaction log full, rollup failed as locked by failed CR). | Remote system | System | any server | /DVD/MON_BW_CL_COL_PC | BW_1HOUR | 1 Hour |
| BW_QUERY_ERROR | BW: Number of erroneous Queries | number | BW | KPI value displays the total number of erroneous BW Queries (queries which has failed or contains any error). | Remote system | System | any server | /DVD/MON_BW_CL_COL_QUERY_RT | BW_1HOUR | 1 Hour |
| BW_QUERY_LONG_RUN | BW: Number of long-running Queries | number | BW | KPI value displays the total number of long-running BW Queries. By default, if the BW Query is running more than 60 seconds, the collector considers this query as long-running. Thresholds for long-running BW Queries can be defined by Input table '/DVD/MON_BWQLONG'. | Remote system | System | any server | /DVD/MON_BW_CL_COL_QUERY_RT | BW_1HOUR | 1 Hour |
| BW_QUERY_RUNTIME | BW: Number of executed Queries | number | BW | KPI value displays the total number of executed BW Queries in the period defined by Collector's parameter 'TIME_PERIOD_IN_SECS'. By default it checks all BW Query executions in last 5 minutes (300 seconds). | Remote system | System | any server | /DVD/MON_BW_CL_COL_QUERY_RT | BW_1HOUR | 1 Hour |
| BW_RSICCONT_GR12 | BW: Forecast RSICCONT Growth in 12 months | count | BW | The admin table RSICCONT contains one entry per load request, each request goes in one provider. When there are too many rows in table RSICCONT for the same provider, the loads / monitor will generate many ENQ and it will slow down the system. This KPI is a forecasted value in 12 months. Looking at speed of increasing of the number of rows in RSICCONT over a month, a forecasted growth is calculated. The forecast is adjusted every day. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSICCONT | BW_1DAY | 1 Day |
| BW_RSICCONT_MX12 | BW: Forecast RSICCONT Max number of entries per cube in 12months | count | BW | The current number of rows in RSICCONT plus the forecasted growth gives the forecasted number in 12 months (see KPI definition RSICCONT Growth in 12 months). Table /DVD/MON_BWRSICC in the satellite system will give you the number of entries per target. When the current value or forecasted value is above 6-7000, consider using report RSSM_REDUCE_REQUESTLIST (check OSS Note 1431315 - P24: Reducing very large request lists in InfoCubes and DSOs). | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSICCONT | BW_1DAY | 1 Day |
| BW_RSMONMESSPAC | BW: Sum max number of packets for all running PSA | count | BW | When several IP run with high number of packets, it creates many ENQ to process and can overload ENQ processing. If one IP has high number of packets, you will get an alert with KPI BW_IP_MAX_PACKET. But if many IP have an average number of alert, you can be alerted using this KPI | Remote system | System | any server | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 Hour |
| BW_SID_GR12 | BW: Forecast SID Growth in 12 months | count | BW | Forecast of System ID (SID) Growth in 12 months. | Remote system | System | any server | /DVD/MON_BW_CL_COL_SID_GROWTH | BW_1DAY | 1 Day |
| BW_SID_MX12 | BW: Forecast SID Max level in 12 months | count | BW | Forecast of maximum System ID (SID) level in 12 months. | Remote system | System | any server | /DVD/MON_BW_CL_COL_SID_GROWTH | BW_1DAY | 1 Day |
| BW_SSQL_ALLNO | BW: SQL - Total number of subqueries | count | BW | Number of queries on the DB (running SQL statement, op mode 0) to correlate with performance issue if needed. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 Hour |
| BW_SSQL_ALLTIM | BW: SQL - Total time spent on subqueries | s | BW | Cumulated time of all queries running on the DB (running SQL statement, op mode 0) to correlate with performance issue if needed. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 Hour |
| BW_SSQL_SQAR | BW: SQL - Average runtime of small subqueries | s | BW | Queries are split in subqueries, one per cube. Runtime of each subquery are available in table rsddstat_olap for the query with option save all stats. Per definition, small subqueries are scanning less than 10 million rows and returning less than 10.000 rows. This KPI is the average runtime of the small queries. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 Hour |
| BW_SSQL_SQLO | BW: SQL - No of small subqueries long running (eg > 10 SEC) | count | BW | This KPI is the number of small queries running for more than 10sec. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 Hour |
| BW_SSQL_SQNO | BW: SQL - No of small subqueries | count | BW | This KPI is the amount of small subqueries. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 Hour |
| BW_SUBQ_ALLNO | BW: non SQL-Total number of subqueries (BWA or HANA) | count | BW | Number of queries executed on BWA, to find period will too many queries in parallel and look for work around if memory / performance is impacted by this. Eg remove parallelization setting of some queries. It also provide a benchmark, we know what can be achieve without degradation. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| BW_SUBQ_ALLTIM | BW: non SQL-Total time spent on subqueries (BWA or HANA) | s | BW | Cumulated time spent on BWA of all subqueries. Also to know if we are reaching some limit. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| BW_SUBQ_SQAR | BW: non SQL-Average runtime of small subqueries (BWA or HANA) | s | BW | When using op mode 2 in BWA, queries are split in subquery, one per cube. Per definition, Small subqueries are scanning less than 10 million rows and returning less than 10.000 rows. Those should run for 1sec on BWA. This indicator calculates the average BWA runtime of small queries. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| BW_SUBQ_SQLO | BW: non SQL-No of small subqueries long run. (eg>10SEC) eg BWA | count | BW | Per definition, Small subqueries are scanning less than 10 million rows and returning less than 10.000 rows. If the average is slow, to appreciate the impact, this KPI provides the number of subqueries running for more than 10sec. If there are 5 or 10.000 subqueries running too slow, the impact on the business is not the same. | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| BW_SUBQ_SQNO | BW: non SQL-No of small subqueries (BWA or HANA) | count | BW | This KPI is the amount of small subqueries (non SQL). | Remote system | System | any server | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 Minutes |
| CPU_IDLE | CPU true idle | % | OS | Times in which the CPU had no task to perform or was waiting for an input/output. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_IDLE_SYS_MIN | Minimum of CPU true idle (all servers) | % | OS | Times in which the CPU had no task to perform or was waiting for an input/output. This value displays the minimum value from all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_LOAD1 | CPU Load (1min): Average of active processes | count | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 1 minute. In SAP, you can see this indicator with OS07, in Linux with the uptime command. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 Minute |
| CPU_LOAD15 | CPU Load (15min): Average of active processes | count | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 15 minutes. In SAP, you can see this indicator with OS07, in Linux with the uptime command. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | N/A - need to schedule this KPI manually* | Custom |
| CPU_LOAD15_P | CPU Load (15min): Percentage of CPUs for active processes | % | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 15 minutes. In SAP, you can see this indicator with OS07, in Linux with the uptime command. This KPI calculates the percentage of the CPU Load average over the last 15 minutes divided by the number of existing CPUs. High numbers indicate potentially overload of the CPUs. On Hardware with multi-threaded CPUs, the number of logical CPU is used (e.g. 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 should be considered during judgements). | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | N/A - need to schedule this KPI manually* | Custom |
| CPU_LOAD1_P | CPU Load (1min): Percentage of CPUs for active processes | % | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 1 minute. In SAP, you can see this indicator with OS07, in Linux with the uptime command. This KPI calculates the percentage of the CPU Load average over the last 1 minute divided by the number of existing CPUs. High numbers indicate potentially overload of the CPUs. On Hardware with multi-threaded CPUs, the number of logical CPU is used (e.g. 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 should be considered during judgements). | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 Minute |
| CPU_LOAD1_P_SYS_MAX | CPU Load (1min): Max. % of CPUs for active processes | % | OS | Based on the KPI 'CPU_LOAD1_P', this KPI represents the maximum percentage of CPUs for active processes from all existing servers for one SAP system (the highest value is reported). | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 Minute |
| CPU_LOAD5 | CPU - Average processes waiting (5 min) | count | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 5 minutes. In SAP, you can see this indicator with OS07, in Linux with the uptime command. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_LOAD5_P | CPU Load (5min): Percentage of CPUs for active processes | % | OS | CPU load average is the average number of processes that are ready for execution (being executed or waiting to be executed by CPU) in the operating system run queue over the last 5 minutes. In SAP, you can see this indicator with OS07, in Linux with the uptime command. This KPI calculates the percentage of the CPU Load average over the last 5 minutes divided by the number of existing CPUs. High numbers indicate potentially overload of the CPUs. On Hardware with multi-threaded CPUs, the number of logical CPU is used (e.g. 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 should be considered during judgements). | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_LOAD5_PMAX | CPU Load (5min): Max. % of CPUs for active processes | % | OS | Based on the KPI 'CPU_LOAD5_P', this KPI represents the maximum percentage of CPUs for active processes from all existing servers for one SAP system (the highest value is reported). | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_NBR | Number of CPU's | count | OS | The number of CPU's is displayed by this KPI. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 Day |
| 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 | 5 Minutes |
| CPU_SYS_MAX | CPU - Maximum used by system (all servers) | % | OS | This KPI shows the maximum percentage usage of CPU used by system from all monitored servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| 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 | 5 Minutes |
| CPU_USER_MAX | CPU - Maximum used by user (all servers) | % | OS | This KPI shows the maximum percentage usage of CPU used by user from all monitored servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_WAIT | CPU IO 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 capture for the database and for all application servers. The chart displays only the worst value (usually IO wait of the database, IO wait on AS is usually zero). | Remote server | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CPU_WAIT_MAX | CPU IO wait (max. in all servers) | % | 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. The value is calculated by CCMS, see transaction ST06.This KPI is max value of the IO wait for all monitored servers for this SID. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| CTS_AGE_OLDESTRQ | CTS - Age of the oldest request in queue | min | SAPSYS | Age of the oldest transport request in queue. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 Day |
| CTS_COUNT_REQNM | CTS - Number of requests not moving in queue | count | SAPSYS | This KPI is number of transport request in import queue which are not imported (their state did not change) since the last snapshot (monitored run). Too many not imported transports could indicate problem with import queue or with automatic imports. If the value of this KPI decreases and indirectly correlates with some incident, it means that on the system were imported transports that affected given problem. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1HOUR | 1 Hour |
| CTS_RC0000A | CTS - Number of imported transports | count | SAPSYS | Number of all imported transport requests. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 Day |
| CTS_RC0008 | CTS - Number of imported transports with RC = 8 | count | SAPSYS | Number of transport request with RC = 8. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 Day |
| CTS_RC0008A | CTS - Number of imported transports with RC >= 8 | count | SAPSYS | Number of imported transport request with RC >= 8. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 Day |
| CTS_RC0012A | CTS - Number of imported transport with RC >= 12 | count | SAPSYS | Number of imported transport requests with RC >= 12. | Remote system | System | any server | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 Day |
| DB_CPU_LOAD5_P | DB CPU Load (avg 5 min) per CPU | % | DB | This KPI represents the average CPU load in 5 min. The value is calculated by CCMS (transaction ST06N), where the CPU load in 5 minutes is divided by the number of CPU. | Remote system | System | any server | /DVD/MON_CL_COL_DB_CPULOAD | DEF_5MIN | 5 Minutes |
| DB_CRIT_TAB_SP_P | Used space on most critical data file (tablespace) | % | DB | KPI displays percentage of used space that has most critical data file of database available. Most critical data file (table space) is chosen by size, so the data file (table space) with smallest free size to extend is critical file. For files that do not have maximum size set, size of logical device the file resides upon is used. Percentage is then calculated from this size. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_5MIN | 5 Minutes |
| DB_FREE | Free size of database | MB | DB | This KPI displays the free size on the database. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_INDEX_NUM | Total number of indexes | count | DB | This KPI contains information about the total number of indexes. An Index is a copy of database table having few numbers of fields. This copy is always in sorted form. As we know, Sorted data would always have a speed access from a database table. Hence, we use an index for the table while reading the database records. Index also contains a pointer pointing towards 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 Index, Secondary Index | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_INDEX_SIZE | Total size of indexes | MB | DB | This KPI describes how total size can be acquire by indexes. You might found the total size of indexes in DBACOCKPIT. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_SIZE | Size of database | MB | DB | Database size contains: number of records in tables, table columns and their sizes, indexes in the model, tablespaces in the model and DBMS and its storage options. All these factors affect size of database and are included into this KPI. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_TAB_NUM | Total number of tables | count | DB | This KPI measures how many tables are in the database. Each database has several tables. Table is one of basic database objects, which main role is storing data into memory space of relational database. Information about total numbers of tables can be found in DBACOCKPIT. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_TAB_SIZE | Total size of tables | MB | DB | This KPI displays actual value of size all tables. The current table sizes are determined by a report and saved in a database table which forms the history of table sizes and table growth. https://help.sap.com/saphelp_nw73/helpdata/en/f4/fdc0c572a14a5a8694ad33a844b50e/content.htm?no_cache=true | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_TRIGGER_CNT_ALL | Number of all DB Triggers | number | DB | KPI value represents the number of all available DB triggers on the system. | Remote system | System | any server | /DVD/MON_CL_COL_DB_TRIGGERS | DEF_1HOUR | 1 Hour |
| DB_TRIGGER_CNT_INVALID | Number of Invalid DB Triggers | number | DB | KPI value represents the total number of all invalid DB triggers on the system. | Remote system | System | any server | /DVD/MON_CL_COL_DB_TRIGGERS | DEF_1HOUR | 1 Hour |
| DB_TRIGGER_CNT_VALID | Number of valid DB Triggers | number | DB | KPI value represents the total number of all valid DB triggers on the system. | Remote system | System | any server | /DVD/MON_CL_COL_DB_TRIGGERS | DEF_1HOUR | 1 Hour |
| DB_TS_FREE | Free size of DB Tablespaces | MB | DB | This KPI calculates the sum of all free sizes of tablespaces in database. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_TS_TOTAL | Size of DB Tablespaces | MB | DB | This KPI calculates the total size of all tablespaces in database. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_TS_USED_P | Used size of DB tablespaces | % | DB | This KPI displays the percentage of used size of all tablespaces in database. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_USED | Used size of database | MB | DB | This KPI displays the used database size in MB. It is calculated as a total DB size minus DB free space available. Threshold values depend on the used DB system and customer's needs. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| DB_USED_P | Used space on database | % | DB | This KPI displays the percentage of used space on database. | Remote system | System | any server | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 Day |
| 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, then 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 | 1 Minute |
| DEQ_ALL_REQ_CNT | Number of releases for all locks of LUW | count | SAPSYS | A database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. If you execute SAP transaction to change database objects, these objects get locked beforehand to prevent being accessed by other users or transactions, and they get released after database commit or database rollback. This KPI counts number of these releases. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| DEQ_ERROR_CNT | Number of errors that occurred when releasing locks | 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 affected by these statements. You can only set a lock for an existing database entry, since the lock mechanism uses a lock flag in the entry. These flags are automatically deleted in each database commit. Database locks are therefore never available longer than for only one database LUW. That means that in ABAP application programming, database locks can no longer exist than the duration of one dialog step. If there are some errors when releasing locks, this KPI counts the number of these errors. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| DEQ_REQUEST_CNT | Number of released requests (DEQUEUE) | count | SAPSYS | A lock object definition contains the database tables and their key fields on the basis of which you want to set a lock. When you create a lock object, the system automatically generates two function modules with the names ENQUEUE_Name and DEQUEUE_Name. You can then set and release SAP locks in your ABAP program by calling these function modules in a CALL FUNCTION statement - this KPI counts the number of dequeue release requests. You can see lock statistics in SM12 Extras -> Statistics. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| DISK_AVG_WAIT | Average disk wait (server) | ms | OS | This KPI calculates the average disk wait on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| DISK_RESPONSE | Disk response time (server) | ms | OS | This KPI displays the disk response time on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| 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 | 5 Minutes |
| DISK_UTIL | Disk utilization (server) | % | OS | This KPI displays disk utilization on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| DISK_UTIL_SYS | Average disk utilization (all servers) | % | OS | This KPI displays disk utilization on all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| DISK_WAIT_SYS | Average disk wait time (all servers) | ms | OS | This KPI displays average disk wait time on all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| DUMP_ALL_WITH_DETAILS | Number of new ABAP runtime errors (DUMPs) | count | SAPSYS | This KPI calculates the number of new ABAP runtime errors (DUMPs) since last run of the collector job. | Remote system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 Day |
| DUMP_AUTH_ERR | Number of Runtime errors (DUMPs) failed on authorization | count | SAPSYS | This KPI represents the number of occurred ABAP runtime errors (DUMPs) due to the missing authorization with following error ID: This value is calculated from the last monitoring snapshot. By default, all runtime errors are counted from all system clients. If you want to count only runtime errors occurred on the current client, you need to set the collector's parameter COLLECT_FROM_ALL_CLIENTS to empty value. | Remote system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 Hour |
| DUMP_DBIF | Number of ABAP Runtime errors (DUMPs) for SQL operations | count | SAPSYS | This KPI calculates the number of occurred ABAP runtime errors (DUMPs) due to the failed SQL operation and error ID starting with 'DBIF*'. This value is counted from last monitoring snapshot. By default, all runtime errors are counted from all system clients. If you want to count only runtime errors occurred on the current client, you need to set the collector's parameter COLLECT_FROM_ALL_CLIENTS to empty value. | Remote system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 HOUR |
| DUMP_NBR | Number of ABAP Runtime errors (DUMPs) on the server | count | SAPSYS | This KPI calculates the number of occurred ABAP runtime errors (DUMPs) on the specific server since the last run of the collector job. | Remote system | Server | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 Day |
| DUMP_NBR_SUM | Number of ABAP Runtime errors (DUMPs) (all servers) | count | SAPSYS | This KPI calculates the number of occurred ABAP runtime errors (DUMPs) on all servers since the last run of the collector job. | Central system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 Day |
| DUMP_RFC_ERR | Number of ABAP Runtime errors (DUMPs) with RFC error | count | SAPSYS | This KPI calculates the number of occurred ABAP runtime errors (DUMPs) on all servers since the last run of the collector job due to the RFC error. | Remote system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 Hour |
| DUMP_SYNTAX_ERR | Number of ABAP Runtime errors (DUMPs) with syntax error | count | SAPSYS | This KPI calculates the number of occurred ABAP runtime errors (DUMPs) due to the syntax errors with following error ID: By default, all runtime errors are counted from all system clients. If you want to count only runtime errors occurred on the current client, you need to set the collector's parameter COLLECT_FROM_ALL_CLIENTS to empty value. | Remote system | System | any server | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 Hour |
| EM_USED_P | Extended memory used | % | OS | This KPI displays the amount of Extended Memory used on the specific server. Extended Memory (EM) contains objects associated with individual users and their open (running) transactions - transaction data such as variables, lists, and internal tables. If the work process requires still more space after using up all available Extended Memory and Roll Area, the system is forced to allocate local Heap Memory. | Remote system | Server | only application server | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 Minutes |
| EM_USED_P_SYS_MAX | Maximum of extended memory used (all servers) | % | OS | This KPI displays the maximum amount of Extended Memory used on all server. Extended Memory (EM) contains objects associated with individual users and their open (running) transactions - transaction data such as variables, lists, and internal tables. If the work process requires still more space after using up all available Extended Memory and Roll Area, the system is forced to allocate local Heap Memory. | Central system | System | any server | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 Minutes |
| ENQ_ARG_MAX_CNT | Maximum number of lock entries that can occur in lock table | count | SAPSYS | This KPI displays the maximal number of different 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 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 | 5 Minutes |
| ENQ_ARG_MAX_LVL | Highest number of different lock arguments in the lock table | count | SAPSYS | This KPI represents the highest number of different lock arguments in the 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 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 | 5 Minutes |
| ENQ_ARG_NOW_LVL | Current number of different lock arguments in the lock table | count | SAPSYS | This KPI calculates the number of all 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 generated from the lock object definition. 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, lock mode, 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 | 5 Minutes |
| ENQ_BACKUP_REQ | Number of update calls for which locks were forwarded | count | SAPSYS | This KPI calculates the number of update calls for which locks were forwarded. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_CLEAN_REQ | Number of releases for all locks of an application server | count | SAPSYS | This KPI calculates the number of all releases of all locks of a selected application server. 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 | 5 Minutes |
| ENQ_ENTR_MAX_CNT | Maximum number of elementary locks in the lock table | count | SAPSYS | This KPI displays the maximal number of elementary locks in the lock table. 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, lock mode, name, and the fields in the locked table. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_ENTR_MAX_LVL | Highest number of elementary locks in the lock table | count | SAPSYS | This KPI displays the highest number of elementary locks in the lock table. 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, lock mode, name, and the fields in the locked table. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| 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. 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, lock mode, name, and the fields in the locked table. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_ENTR_P | Usage of SAP lock table | % | SAPSYS | This KPI calculates the percentage of lock table usage. 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 (see Lock Collisions). If this is the case, the request is rejected. Otherwise, the new lock is written to the lock table. | Central system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_ERROR_CNT | Number of errors that occurred during lock requests | count | SAPSYS | This KPI calculates the number of errors that occurred during lock requests. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_FILE_WRITE | Number of write accesses to file | count | SAPSYS | This KPI calculates the number of write accesses to file. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_FILE_WRT_BCK | Number of write accesses to backup file | count | SAPSYS | This KPI calculates the number of write accesses to backup file. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_OWN_MAX_CNT | Maximum number of lock owner IDs in the lock table | count | SAPSYS | This KPI calculates the maximal number of lock owner IDs in the lock table. 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 | 5 Minutes |
| 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. 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 | 5 Minutes |
| ENQ_OWN_NOW_LVL | Current number of lock owners in the lock table | count | SAPSYS | This KPI calculates the current number of all lock owners stored in the lock table. Lock owner is a person who holds a lock. A lock can have one or two owners. To find out which user is currently holding a lock, use function module ENQUEUE_<Name>. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_REPORT_REQ | Number of operations for reading the lock table | count | SAPSYS | This KPI calculates the number of operations for reading the lock table. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_REQUEST_CNT | Number of lock requests | count | SAPSYS | This KPI calculates the number of lock requests. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_REQUEST_CNTD | Number of lock requests per minute since last run | */min | SAPSYS | This KPI calculates the delta between the value of ENQ processed at last snapshot and the current value, divided by the number of minutes since the last snapshot to calculate a number of ENQ processed per minute. If we have high number of WP in SAPLSENA and number of ENQ per minute is high, the issue is that the application is raising too many ENQ. Solution is to find the root cause of high number of ENQ, can be too packets (eg. too many small packets) or too many requests in rsiccont. It is useful to monitor this number on parallel processes. | Central system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_REQ_REJ_CNT | Number of rejected lock requests | count | SAPSYS | This KPI calculates the number of rejected lock requests. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_REQ_REJ_CNTD | Number of rejected lock requests per minute since last run | */min | SAPSYS | This KPI calculates the number of rejected lock requests per minute since last run. | Central system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_TOTAL_TIME | Total time spent in the critical path for lock operations | s | SAPSYS | This KPI calculates the total time spent in the critical path for lock operations. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_TOTAL_WAIT | Total wait time of par. proc. before entering critical path | s | SAPSYS | This KPI calculates the total wait time of parallel processing before entering critical path. Waiting time for all work processes for accessing lock table. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| ENQ_TOT_SER_TIME | Total time spent in the enqueue server | s | SAPSYS | This KPI calculates the total time spent in the enqueue server. 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 | 5 Minutes |
| ENQ_UPD_MAX_CNT | Max. num. of open update req. with locks occurred so far | count | SAPSYS | This KPI calculates the maximal number of accumulated update requests. | Remote system | System | any server | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 Minutes |
| 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 | 5 Minutes |
| FBA_APPLOGSIZE | Application log size (total) | MB | SAPSYS | This KPI value represents the total size of 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 | 1 Day |
| FBA_BATCHINLG | Batch input session and log size (total) | MB | SAPSYS | This KPI value represents the total size of following tables: APQD - Data definition queue APQI - Queue info definition APQL - Batch Input log directory | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_BATCHJOB | Batch job size (total) | MB | SAPSYS | This KPI value represents the total size of 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 | 1 Day |
| FBA_CHPOINTSIZE | Change pointer size (total) | MB | SAPSYS | This KPI value represents the total size of following tables: BDCP - Change pointer BDCP2 - Aggregated Change Pointers (BDCP, BDCPS) BDCPS - Change pointer status | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_DBTABLOGSIZE | Table log size (total) | MB | SAPSYS | This KPI value represents total size of table DBTABLOG - Log Records of Table Changes. | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_ORPHJOBLG | Orphaned job logs size (total) | MB | SAPSYS | This KPI value represents the total size of table TST01- TemSe: List of objects and parts. | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_RFCLOGSIZE | RFC log size (total) | MB | SAPSYS | This KPI value represents the total size of 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 | 1 Day |
| FBA_SNAPSIZE | Size of ABAP Snapshot for Runtime Errors | MB | SAPSYS | This KPI value represents the total size of table SNAP - ABAP/4 Snapshot for Runtime Errors. | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_SPOOLREQSIZE | Spool request size (total) | MB | SAPSYS | This KPI value represents the total size of following tables: TSP01 - Spool Requests TST03 - TemSe data | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_TEMSEFILES | Orphaned TemSe on DB size (total) | MB | SAPSYS | This KPI value represents the total size of table TST03 - TemSe data. | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBA_UPDREQSIZE | Update request size (total) | MB | SAPSYS | This KPI value represents the total size of following tables: VBDATA - Update data VBHDR - Update header VBMOD - Update function modules | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BASIS | 1 Day |
| FBW_BGPROC_SIZE | BW background process size (total) | MB | BW | This KPI value represents the total size of following BW Batch Management tables: RSBATCHCTRL - Control Table RSBATCHDATA - Copy of INDX for Batch and Enqueue Runtime Data RSBATCHHEADER - Header Table for the Start Process RSBATCHPROT - Log Table | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BW | 1 Day |
| FBW_CHLG | Change Log size (total) | MB | BW | This KPI value represents the total size of all BW changelog tables. | Remote system | System | any server | /DVD/MON_BW_CL_COL_PSACHLG | FS_BW | 1 Day |
| FBW_PSA | PSA table size (total) | MB | BW | This KPI value represents the total size of all PSA tables. | Remote system | System | any server | /DVD/MON_BW_CL_COL_PSACHLG | FS_BW | 1 Day |
| FBW_STAT_SIZE | BW statistics size (total) | MB | BW | This KPI value represents the total size of BW statistics (OLAP) tables: RSDDSTATAGGR - Statistics data BW for aggregate selection and accounting RSDDSTATAGGRDEF - Navigation step / aggregate definition RSDDSTATCOND - Data on Condensing Run Info Cube RSDDSTATDELE - Data on Deletion of Data in Info Cube RSDDSTATDM - Data Manager Query Statistic Records RSDDSTATDTP - Table for WHM Statistics. Details DTP RSDDSTATEVDATA - Key Figures for the Events RSDDSTATHEADER - Information by Runtime Object RSDDSTATINFO - Information by Navigation Step RSDDSTATLOGGING - Logging Table for OLAP Statistics (new) | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_BW | 1 Day |
| FER_IDOC_SIZE | IDoc size (total) | MB | ERP | This KPI value represents the total size of following tables: EDID4 IDoc Data Records from 4.0 onwards EDIDC Control record (IDoc) EDIDS Status Record (IDoc) | Remote system | System | any server | /DVD/MON_CL_COL_TAB | FS_ERP | 1 Day |
| FER_WF_ITEM_SIZE | Workflow item size (total) | MB | ERP | This KPI value represents the total size of 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 ofNodes 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 | 1 Day |
| FS_ROOT_FREE | Free space monitoring on root partition | % | OS | This KPI calculates the percentage of free space on the root partition. This KPI serves as an example based on which you might define custom KPIs for monitoring free space on any partition. | Remote system | Server | only application server | /DVD/MON_CL_COL_SYS_FS | N/A - need to schedule this KPI manually* | Custom |
| GRC_AOC_BC_ALL | Number of SAP_BC roles having full auth. on org. level | count | GRC | This KPI displays the number of all SAP_BC roles which have the full authorization on the organization level. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 Day |
| GRC_AOC_SEC_ALL | Number of SAP_SEC_ roles having full auth. on org. level | count | GRC | This KPI displays the number of all roles (starting with SAP_SEC_*) which have the full authorization on the organization level. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 Day |
| GRC_AOC_ZCOM_ALL | Number of X,Y,Z* roles having full auth. on company code | count | GRC | This KPI displays the number of all custom roles (starting with X,Y,Z*) which have the full authorization on company code. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 Day |
| GRC_AUTH_ALL | Number of user with full authorization (SAP_ALL,SAP_NEW) | count | GRC | This KPI displays the number of all users which have the full authorizations (SAP_ALL, SAP_NEW) | Remote system | System | any server | /DVD/MON_GRC_CL_COL_USR_AUTH | GRC_1DAY | 1 Day |
| GRC_AUTH_ALL_O_N | Number of NEW users with full authorization(SAP_ALL,SAP_NEW) | count | GRC | This KPI displays the number of new identified users since the last run of the collector's execution, which have the full authorizations (SAP_ALL, SAP_NEW) | Remote system | System | any server | /DVD/MON_GRC_CL_COL_USR_AUTH | GRC_1DAY | 1 Day |
| GRC_PROF_PARAM | Number of profile parameters with unexpected values | count | GRC | This KPI displays the number of parameter which have different values as values specified in the input table '/DVD/MON_GRC_I1'. The collector checks the values of profile parameters and compare them with values defined in input table. The comparison is performed for each server. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_PARAM | GRC_1DAY | 1 Day |
| GRC_REF_USR_CNT | Number of used reference users | count | GRC | This KPI displays the number of used reference users on your system. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_REF_USERS | GRC_1DAY | 1 Day |
| GRC_SEC_NOTE_CNT | Number of not implemented security notes | count | SAPSYS | This KPI displays the number of not implemented SAP security notes. To be able to monitor this KPI, you need to specify RFC destination to your Solution Manager. You might specify this RFC destination with the collector's parameter 'SOLMAN_RFC_DESTINATION'. | Remote system | System | any server | /DVD/MON_GRC_CL_COL_SEC_NOTES | GRC_1DAY | 1 Day |
| HDB_ALERT_ERROR | HANA alert type - error | count | HANA | This KPI calculates the number of HANA alerts with 'Error' priority. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_ALERT | HDB_5MIN | 5 Minutes |
| HDB_ALERT_HIGH | HANA alert type - high | count | HANA | This KPI calculates the number of HANA alerts with 'High' priority. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_ALERT | HDB_5MIN | 5 Minutes |
| HDB_ALERT_INFORMATION | HANA alert type - information | count | HANA | This KPI calculates the number of HANA alerts with 'Information' priority. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_ALERT | HDB_5MIN | 5 Minutes |
| HDB_ALERT_LOW | HANA alert type - low | count | HANA | This KPI calculates the number of HANA alerts with 'Low' priority. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_ALERT | HDB_5MIN | 5 Minutes |
| HDB_ALERT_MEDIUM | HANA alert type - medium | count | HANA | This KPI calculates the number of HANA alerts with 'Medium' priority. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_ALERT | HDB_5MIN | 5 Minutes |
| HDB_BCK_DELAY_D | Time since last successful DATA backup | h | HANA | This KPI calculates the time since the last successful DATA backup. A backup, or the process of backing up, refers to the copying and archiving of data so it may be used to restore the original after a data loss event. Data backups contain the current payload of the data volumes (data and undo information). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_BCK_DELAY_L | Time since last successful LOG backup | s | HANA | This KPI calculates the time since last successful LOG backup. By default, automatic log backups are enabled in SAP HANA. Backup log is a feature of backup applications that records the events that occur during a backup process. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_BCK_FAILED | Number of failed backups | count | HANA | This KPI calculates the number of failed backups. Media failure, human error and hardware failure are among the most common reasons of backup failures. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_BCK_FAIL_DAT | Number of failed DATA backups | count | HANA | This KPI calculates the number of failed DATA backups. KPI recognized two classifications of DATA failure: failure on 'complete data backup' and 'data snapshot'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_BCK_FAIL_LOG | Number of failed LOG backups | count | HANA | This KPI calculates the number of failed LOG backups. KPI recognized two classifications of LOG failure: failure on 'log backup' and 'log missing'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_CPU_HOST | CPU utilization per host (avg 5 mins) | % | HANA | The CPU utilization will always sum up to 100%. User utilization should not exceed a value of 50 to 60%. System utilization should be below 20%,and Idle time should be above 20%. The max CPU utilization is the utilization of the most of the possible CPU. Maximal CPU utilization per host displays average utilization calculated every 5 minutes. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_MAX_P | Max CPU utilization on all hosts (avg 5 mins) | % | HANA | This KPI displays the average utilization calculated every 5 minutes. The CPU utilization will always sum up to 100%. User utilization should not exceed a value of 50 to 60%. System utilization should be below 20%, and Idle time should be above 20%. The max CPU utilization is utilization of the most of the possible CPU. Maximal CPU utilization on all hosts is measured by this KPI. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_SYS_P | CPU utilization by system (avg 5 mins) | % | HANA | This KPI displays the utilization of CPU by system calculated every 5 minutes. System utilization of CPU should be below 20%. System CPU time is the time spent running code in the operating system kernel on behalf of your program. When the value of system utilization rise up above 20%, it can signalize some failures. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_SYS_SER | CPU utilization by system per host (avg 5 mins) | % | HANA | This KPI calculates the utilization by system on the specific host. System utilization of CPU should be below 20%. System CPU time is the time spent running code in the operating system kernel on behalf of your program. When the value of system utilization rise up above 20%, it can signalize some failures. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_USR_P | CPU utilization by users (avg 5 mins) | % | HANA | This KPI displays situation, when CPU is utilized by user. In this situation, the average utilization is calculated every 5 minutes. User utilization should not exceed a value of 50 to 60%. User CPU time is time spent on the processor of running program's code (or codes in libraries). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_USR_SER | CPU utilization by users per host (avg 5 mins) | % | HANA | When the CPU is utilized by users per server, this KPI calculates the utilization every 5 minutes. User utilization should not exceed a value of 50 to 60%. User CPU time is time spent on the processor of running your program's code (or codes in libraries). | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_UTIL_P | Total CPU utilization (avg 5 mins) | % | HANA | This KPI displays the HANA total host CPU utilization measured in 5 minutes intervals. The data collected from M_HOST_RESOURCE_UTILIZATION presents the true average utilization per monitoring cycle. The key benefit of this KPI is: short term peaks will not cause unnecessary alarms. Because of the logic, alerting thresholds must be configured with lower values compared to peak value monitoring (E.g. threshold at 60% where peaks can breach 90%). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_WIO_P | CPU utilization in I/O waits (avg 5 mins) | % | HANA | This KPI displays the CPU utilization in I/O waits. I/O wait is the total time that working processes are blocked, waiting for the I/O operation to complete. An I/O operation is a request to retrieve or write data to the storage. The total time that it takes to complete all I/O operations is I/O operation time. I/O wait happens due to heavy load on the system. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CPU_WIO_SER | CPU utilization in I/O waits per host (avg 5 mins) | % | HANA | This KPI calculates the CPU utilization in I/O waits per specific host. I/O wait is the total time that working processes are blocked, waiting for the I/O operation to complete. An I/O operation is a request to retrieve or write data to the storage. The total time that it takes to complete all I/O operations is I/O operation time. I/O wait happens due to heavy load on the system. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 Minutes |
| HDB_CS_DELRATIO | Delta memory / Total memory ratio | % | HANA | This KPI displays the percentage of delta memory versus total memory used. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_DELTASIZE | Size of column tables in delta memory | MB | HANA | This KPI displays the total size of column table data in delta memory. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_ESTIMSIZE | Estimated size of column tables | MB | HANA | This KPI displays the estimated size of column tables in memory. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_H_ESTSIZE | Estimated size of column tables per host | MB | HANA | This KPI displays the estimated size of column tables in memory for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_H_TOTSIZE | Total memory size of column tables per host | MB | HANA | This KPI value calculates the total memory size of column tables per host. By default, it does not include the persistent memory size (available since release 2.00.040). You might set the collector's parameter INCLUDE_PERS_MEMORY_SIZE to 'X' to include also persistent memory size into this KPI value. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_MAINSIZE | Size of column tables in main memory | MB | HANA | This KPI displays the size of column tables in the main memory. Under normal circumstances, the SAP HANA database manages the loading and unloading of tables into and from memory independently, the aim being to keep all relevant data in memory. However, you can manually load and unload individual tables, as well as load table columns if necessary. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_TOTALSIZE | Total memory size of column tables | MB | HANA | This KPI value calculates the total memory size of column tables. By default, it does not include the persistent memory size (available since release 2.00.040). You might set the collector's parameter INCLUDE_PERS_MEMORY_SIZE to 'X' to include also persistent memory size into this KPI value. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_UNLOADS | Number of unloads | count | HANA | This KPI calculates the number of unloads. The UNLOAD statement unloads the column store table from memory. This can be done to free up memory. The table will be loaded again on next access. The UNLOAD statement unloads the column store table from memory. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_UNLOADS04 | Number of unloads priority 0 to 4 due to low memory | count | HANA | This KPI displays the number of unloads with priority 0 to 4. Priority 0 to 4 is the most important priority of all priorities (9 priorities). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_UNLOADS56 | Number of unloads priority 5 to 6 due to low memory | count | HANA | This KPI displays the number of unloads with priority 5 to 6. Priority 5 to 6 is in the middle of importance from all priorities (9 priorities). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_UNLOADS79 | Number of unloads priority 7 to 9 due to low memory | count | HANA | This KPI displays the number of unloads with priority 7 to 9. Priority 7 to 9 is at least important from all priorities (9 priorities). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_CS_UNLOADSL | Number of unloads due to low memory | count | HANA | This KPI calculates the number of unload due to the low memory (such records can be found in view M_CS_UNLOADS with reason 'LOW_MEMORY'). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_DISK_DATA | Used space on data disk per host | % | HANA | This KPI displays the used space on data disk per server. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)Used space on data disk is the amount of disk space used on the host's hard disk as a whole. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_DBCK | Used space on data backup disk per host | % | HANA | This KPI displays the used space on data backup disk per server. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service, Storage type (data, log, trace)a backup, or the process of backing up, refers to the copying and archiving of data so it may be used to restore the original after a data loss event. Data backups contain the current payload of the data volumes (data and undo information). | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_D_TOTAL | Total size of data disks | GB | HANA | This KPI displays the total space on data disk (absolute value in GB). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_D_USED | Total used size on data disks | GB | HANA | This KPI displays the used space on data disks (absolute value in GB). | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minues | ||
| HDB_DISK_LBCK | Used space on log backup disk per host | % | HANA | This KPI displays the used space on log backup disk per host. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk: Service, Storage type (data, log, trace) By default, automatic log backups are enabled in SAP HANA. Backup log is a feature of backup applications that records the events that occur during a backup process. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_LOG | Used space on log disk per host | % | HANA | This KPI displays the used space on log disk per server. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)The size of the transaction log must be checked regularly to work out how much free space is available on the log disk. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_L_TOTAL | Total size of log disks | GB | HANA | This KPI displays the total space on log backup disk (absolute value in GB). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_L_USED | Total used size on log disks | GB | HANA | This KPI displays the used space on log disk (absolute value in GB). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_MAXDATA | Max. used space on data disks | % | HANA | This KPI displays the maximum of used space on data disk. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)Used space on data disk is the amount of disk space used on the host's hard disk as a whole. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_MAXDBCK | Max. used space on data backup disks | % | HANA | This KPI displays the maximum of used space on data backup disks. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)A backup, or the process of backing up, refers to the copying and archiving of data so it may be used to restore the original after a data loss event. Data backups contain the current payload of the data volumes (data and undo information). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_MAXLBCK | Max. used space on log backup disks | % | HANA | This KPI displays the maximum of used space on log backup disks. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)By default, automatic log backups are enabled in SAP HANA. Backup log is a feature of backup applications that records the events that occur during a backup process. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_MAXLOG | Max. used space on log disks | % | HANA | This KPI displays the maximum used space on log disks. Monitoring of disk space includes: disk usage, volume size and other disk activity statistics on the Volumes tab of the Administration editor. There are two views available on the Volumes tab for monitoring the size of volumes on disk : Service Storage type (data, log, trace)The size of the transaction log must be checked regularly to work out how much free space is available on the log disk. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DISK_MAXUSED | Max. used disk space | % | HANA | This KPI displays the maximum size of the host's hard disk. This is the highest percentage of all the disk usage. If low, means no issue on all the disks, no need to check them one by one. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 Minutes |
| HDB_DM_COUNT | Number of small delta merge running for more than 60secs | count | HANA | This KPI displays the number of small delta merge running for more than 1 minute. Write operations are only performed on the delta storage. In order to transform the data into a format that is optimized in terms of memory consumption and read performance, it has to be transferred to the main storage. This is accomplished by a process called delta merge. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DM | HBD_5MIN | 5 Minutes |
| HDB_DM_MAXRUN | Max. duration of small delta merge | s | HANA | This KPI displays the duration of a small delta merge. Write operations are only performed on the delta storage. In order to transform the data into a format that is optimized in terms of memory consumption and read performance, it has to be transferred to the main storage. This is accomplished by a process called delta merge. The whole process of delta merge is carried out at a certain time. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DM | HDB_5MIN | 5 Minutes |
| HDB_DUMPS | Number of HANA dumps | count | HANA | This KPI calculates the number of dump files written by HANA. Should be 0, if there are any files, it means there were out-of-memory situations or crashes. You can view dump files via HANA studio. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_DUMP | HDB_5MIN | 5 Minutes |
| HDB_DUMPS_HOST | Number of HANA dumps per host | count | HANA | This KPI calculates the number of dump files per host written by HANA. Should be 0, if there are any files, it means there were out-of-memory situations or crashes. You can view dump files via HANA studio. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_DUMP | HDB_5MIN | 5 Minutes |
| HDB_FAILOVER | Number of hosts in failover status | count | HANA | Host auto-failover is a local fault recovery solution that can be used as a supplemental or alternative measure to system replication. One (or more) standby hosts are added to a SAP HANA system and configured to work in standby mode. The databases on the standby hosts do not contain any data and do not accept requests or queries as long as they are in standby mode. See SAP Note 2057595 | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_HEAPCSTABLH | HANA Heap Category: Pool/ColumnStoreTables | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/ColumnStoreTables' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPCSTABLH_MAX | HANA Heap Category: Pool/ColumnStoreTables (max all hosts) | MB | HANA | This KPI calculates the maximum size of Heap memory on HANA for category 'Pool/ColumnStoreTables' from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPDEFLPAH | HANA Heap Category: Pool/PersistenceManager/PersistentSpace/ | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/PersistenceManager/PersistentSpace/' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPFLA_ULH | HANA Heap Category: MemoryMapLevel3Nodes | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'MemoryMapLevel3Nodes' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPITABH | HANA Heap category: Pool/itab | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/itab' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPPERSMAH | HANA Heap category: Pool/PersistenceManager | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/PersistenceManager' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPPERSMAH_MAX | HANA Heap category: Pool/PersistenceManager (max all hosts) | MB | HANA | This KPI calculates the maximum size of Heap memory on HANA for category 'Pool/PersistenceManager' from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPPERUTCH | HANA Heap Category: Pool/PersistenceManager/UnifiedTableCont | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/PersistenceManager/UnifiedTableCont' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPROWENGH | HANA Heap Category: Pool/RowEngine | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/RowEngine' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPROWENGH_MAX | HANA Heap Category: Pool/RowEngine (max all hosts) | MB | HANA | This KPI calculates the maximum size of Heap memory on HANA for category 'Pool/RowEngine' from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPSTATSH | HANA Heap Category: Pool/Statistics | MB | HANA | This KPI calculates the size of Heap memory on HANA for category 'Pool/Statistics' for a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPSTATSH_MAX | HANA Heap Category: Pool/Statistics (max all hosts) | MB | HANA | This KPI calculates the maximum size of Heap memory on HANA for category 'Pool/Statistics' from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPTMPQUE | HANA Heap temporary memory used (all hosts) | MB | HANA | This KPI displays the size of temporary used HANA Heap memory for all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_HEAPTMPQUEH | HANA Heap temporary memory used (host) | MB | HANA | This KPI displays the size of temporary used HANA Heap memory on a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_HEAPMEM | HDB_5MIN | 5 Minutes |
| HDB_IO_MINREAD | Min. I/O data read speed | MB/s | HANA | This KPI displays the minimal value of I/O data read speed. To achieve optimal database performance, I/O activity (read/write accesses) should be evenly distributed on the database's hard disks. Value -1 is collected when total size of red data from last execution of collector is less than 5MB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_MINWRITE | Min. I/O data write speed | MB/s | HANA | This KPI displays the minimal value of I/O data write speed. To achieve optimal database performance, I/O activity (read/write accesses) should be evenly distributed on the database's hard disks. Value -1 is collected when total size of written data from last execution of collector is less than 5MB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_RR_DATA | Max. DATA read ratio | % | HANA | This KPI displays the maximum DATA read ratio. I/O calls are executed asynchronously; that is the thread does not wait for the order to return. A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_SER_READ | I/O data read speed per host | MB/s | HANA | This KPI displays the DATA read ratio per host. To achieve optimal database performance, I/O activity (read/write accesses) should be evenly distributed on the database's hard disks. No value is collected when total size of red data from last execution of collector is less than 5MB. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_SER_RR | DATA read ratio per host | % | HANA | This KPI displays the DATA read ratio per host. I/O calls are executed asynchronously; that is the thread does not wait for the order to return. A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_SER_WLOG | LOG write ratio per host | % | HANA | This KPI displays the LOG write ratio per host. I/O calls are executed asynchronously; that is the thread does not wait for the order to return. A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_SER_WR | DATA write ratio per host | % | HANA | This KPI displays the DATA write ratio per host I/O calls are executed asynchronously; that is the thread does not wait for the order to return. A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_SER_WRITE | I/O data write speed per host | MB/s | HANA | This KPI calculates the I/O data write speed per host. I/O calls are executed asynchronously; that is the thread does not wait for the order to return. A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. No value is collected when the total size of written data from the last execution of the collector is less than 5MB. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_WR_DATA | Max. DATA write ratio | % | HANA | This KPI displays the maximal DATA write ratio. I/O calls are executed asynchronously (the thread does not wait for the order to return). A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_IO_WR_LOG | Max. LOG write ratio | % | HANA | This KPI displays the maximal LOG write ratio. I/O calls are executed asynchronously (the thread does not wait for the order to return). A ratio close to 0 says that the thread does not wait at all; a ratio close to 1 means that the thread waits until I/O request is completed because the asynchronous call is blocked (time for triggering I/O time for I/O completion). More information can be found in SAP Note 1930979. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 Minutes |
| HDB_LOG_BUFWAITP | Buffer switches with Wait on buffer semaphore (max all host) | % | HANA | This KPI displays the maximum percentage of buffer switches waiting on buffer semaphore from all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_LOG_BUFWAITT | Number of Buffer switches wait since the last check | count | HANA | This KPI displays the number of buffer switches (wait) since the last execution of the collector. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_LOG_BUFWNOWT | Number of Buffer switches (noWait+wait) since the last check | count | HANA | This KPI displays the number of buffer switches (noWait+wait) since the last execution of the collector. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_LOG_SEG_FREE | Minimum number of Free log segments (all hosts) | count | HANA | This KPI displays the lowest value for Free log segments of service 'indexserver' for all nodes. If this KPI is 0 then the log backup will be delayed and may cause a crash (KPI can be also zero when no corresponding log segment is found for the log buffer record). If this KPI value is low, check detail table 'HANA Log buffer details' on the central system or content of table /DVD/MON_HDBLOGS on the satellite system to identify which node might experience some issues. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_LOG_SEG_TRNC | Maximum number of Truncated log segments (all hosts) | count | HANA | This KPI displays the highest number of truncated log segments from all hosts. If this value is high, see the content of the table /DVD/MON_HDBLOGS to check which host (node) is problematic. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 Minutes |
| HDB_MEM_ALLOCLIM | Global memory allocation limit for the database | GB | HANA | This KPI displays the global memory allocation limit for database in GB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_CACHE_P | Memory used by caches per host | % | HANA | This KPI displays the percentage of host memory used by caches per host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_CS_P | Memory used by column store per host | % | HANA | This KPI displays the percentage of host memory used by column store per host. If this component grows rapidly, consider housekeeping or archiving solutions. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_HOST_P | Used physical memory per host | % | HANA | This KPI calculates the percentage of utilization physical memory per host. Physical memory is the main memory, the RAM. Unlike physical memory, virtual memory can be allocated by the SAP system. The operating system determines if the allocated memory area resides in the physical memory or in the operating system swap/page space. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_MAX_P | Maximum used physical memory (all hosts) | % | HANA | This KPI displays the highest usage of physical memory on all hosts. Physical memory is the main memory, the RAM. Unlike physical memory, virtual memory can be allocated by the SAP system. The operating system determines if the allocated memory area resides in the physical memory or in the operating system swap/page space. Maximum used physical memory around 94% is normal. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SQL_P | Memory used by SQL exec & results per host | % | HANA | This KPI calculates the percentage of host memory used by SQL execution and intermediate results. If this area grows, it can be an indicate too expensive/inefficient SQL statements. Please check list of expensive SQL statements in DB02 transaction. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SQL_P_DB_MAX | Memory used by SQL exec & results (max all hosts) | % | HANA | This KPI calculates the percentage of host memory used by SQL execution and intermediate results from all servers. If this area grows, it can be an indicate too expensive/inefficient SQL statements. Please check list of expensive SQL statements in DB02 transaction. | Central system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SRVHOSTD | Percentage of used service memory per host – Delta | % | HANA | This KPI displays the change (delta) in percentage of used service memory per host. Service used memory - SAP HANA system consists of multiple services that all consume memory, in particular the index server service (the main database service). The index server holds all the data tables and temporary results, and therefore dominates SAP HANA used memory. | Central system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SRVHOSTP | Database memory used per host | % | HANA | This KPI displays the percentage of used service memory per host. SAP HANA system consists of multiple services where each service consumes the memory. This KPI value calculates the used memory for the main database service 'indexserver'. The service 'indexserver' holds all the data tables and temporary results, therefore dominates for SAP HANA used memory. By default, it does not include the persistent memory size. You might set collector's parameter INCLUDE_PERS_MEMORY_SIZE to 'X' to include also persistent memory size into this KPI value. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SRVUSEDP | Maximum database memory used (all hosts) | % | HANA | This KPI calculates the % of max used memory on all hosts. By default, it does not include the persistent memory size. You might set collector's parameter INCLUDE_PERS_MEMORY_SIZE to 'X' to include also persistent memory size into this KPI value. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_STAT_P | Memory used by monitoring & statistics per host | % | HANA | This KPI calculates the percentage of host memory used by monitoring and statistics server. In case of memory growth, please check SAP note 2147247 - FAQ: SAP HANA Statistics Server | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_STAT_P_DB_MAX | Memory used by monitoring & statistics (max all hosts) | % | HANA | This KPI calculates the percentage of host memory used by SQL execution and intermediate results from all servers. If this area grows, it can be an indicate too expensive/inefficient SQL statements. Please check the list of expensive SQL statements in DB02 transaction. | Central system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SYS_P | Memory used by system per host | % | HANA | This KPI calculates the percentage of host memory used by database system (not operating system). If this component grows rapidly, it can be caused by a memory leak in HANA system and has to be fixed by HANA upgrade. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_SYS_P_DB_MAX | Memory used by system (max all hosts) | % | HANA | This KPI displays the maximum percentage of host memory used by database system (not operating system) from all servers. If this component grows rapidly, it can be caused by a memory leak in HANA system and has to be fixed by HANA upgrade. | Central system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_TOTAL | Total physical memory on HANA available | GB | HANA | This KPI displays the total physical memory available on HANA in GB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_USED | Total physical memory used | GB | HANA | This KPI displays the total usage of physical memory. Physical memory is the main memory, the RAM. Unlike physical memory, virtual memory can be allocated by the SAP system. The operating system determines if the allocated memory area resides in the physical memory or in the operating system swap/page space. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_USED_DB | Total memory used by database | GB | HANA | This KPI displays the total memory used by HANA database in GB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MEM_USED_P | Total database memory used | % | HANA | This KPI calculates the percentage of allocated HANA memory used by database. Recommendation is max 50% of memory used for data and rest is reserved for calculation and intermediate results. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 Minutes |
| HDB_MVCC_CL_FILE | HDB MVCC Number of cleanup file | count | HANA | This KPI is collected by using HANA System View M_UNDO_CLEANUP_FILES. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MVCC | HDB_5MIN | 5 Minutes |
| HDB_MVCC_MAXHOST | HDB MVCC Max. number of versions (all hosts) | ver. | HANA | This KPI displays the maximum number of versions using Multiversion Concurrency Control (MVCC). The main advantage to using the MVCC model of concurrency control rather than locking is that in MVCC, locks acquired for querying (reading) data do not conflict with locks acquired for writing data, and so reading never blocks writing and writing never blocks reading. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_MVCC | HDB_5MIN | 5 Minutes |
| HDB_NETSERVRESP | HANA Network Service response time per host | ms | HANA | This KPI displays the service response time per host for HANA Network. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NETSERVRESPM | HANA Network Service response time (max all hosts) | ms | HANA | This KPI displays the highest HANA Network Service response time on all hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_IN | HANA received via network (average per minute) | MB/min | HANA | This KPI calculates the average of read (received) bytes from network per minute on a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_INM | HANA received via network (max. minute avg. from all host) | MB/min | HANA | This KPI calculates the maximum average of read (received) bytes from network per minute from all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_IP | HANA received via network - traffic peak | MB/min | HANA | This KPI calculates the traffic peak of read (received) bytes from network on a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_IPM | HANA received via network - traffic peak from all hosts | MB/min | HANA | This KPI calculates the traffic peak of read (received) bytes from network from all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_OP | HANA sent via network – traffic peak | MB/min | HANA | This KPI calculates the traffic peak of written (sent) bytes to network on a specific host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_OPM | HANA sent via network – traffic peak from all hosts | MB/min | HANA | This KPI calculates the traffic peak of written (sent) bytes to network from all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_OUM | HANA sent via network (max. minute avg. from all host) | MB/min | HANA | This KPI calculates the maximum average of written (sent) bytes to network per minute from all available hosts. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_HOST_OUT | HANA sent via network (average per minute) | MB/min | HANA | This KPI calculates the maximum average speed pf written (sent) bytes to network per minute from all available hosts. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_PING | Index server ping time per host | ms | HANA | This KPI displays the maximum ping time per host. The measured ping times include the communication between nameserver and indexserver. Increased times can be a symptom of an underlying performance issue. Check for general issues impacting the performance (e.g. resource bottlenecks) | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_PING_DB_MAX | Index server ping time (max all hosts) | ms | HANA | This KPI displays the maximum ping time from all hosts. The measured ping times include the communication between nameserver and indexserver. Increased times can be a symptom of an underlying performance issue. Check for general issues impacting the performance (e.g. resource bottlenecks) | Central system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | |
| HDB_NET_RATIO | Network I/O ratio | % | HANA | This KPI displays the Ratio between network time and total client + server time of a request. For example 30% means that in average the request spent 30% of the time on network transfer. If this value is high, it can indicate network bottlenecks. To enable this KPI, you need to set the HANA parameter: indexserver.ini -> [sql_client_network_io] -> enabled. See SAP Note 2222200 - FAQ: SAP HANA Network | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_SPEED | Network throughput | MB/s | HANA | This KPI calculates the average network throughput between HANA clients and servers. To enable this KPI, you need to set the HANA parameter: indexserver.ini -> [sql_client_network_io] -> enabled. See SAP Note 2222200 - FAQ: SAP HANA Network | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_NET_TRAFFIC | Network traffic in last 5 minutes | MB | HANA | This KPI displays the total amount of data transferred via network between HANA clients and servers in last 5 minutes. To enable this KPI, you need to set the HANA parameter: indexserver.ini -> [sql_client_network_io] -> enabled. See SAP Note 2222200 - FAQ: SAP HANA Network | Remote system | System | any server | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 Minutes |
| HDB_OLCK_AGE | Age of the oldest Object Lock | min | HANA | This KPI displays the age of the oldest Object Lock in monitoring view M_OBJECT_LOCKS. Locks are set on HANA objects to guarantee data integrity. It can happen that a lock remains too long (due to bug or bad design) and this will impact users (waiting for a lock to be removed) and operation (too many cleanup file or many threads). Monitoring view M_OBJECT_LOCKS provides the status of currently acquired locks on objects with detailed information such as lock acquisition time or lock mode. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_OBJECTLOCK | HDB_5MIN | 5 Minutes |
| HDB_OLCK_COUNTX | Number of Object Locks older than X minutes | count | HANA | This KPI displays the number of object lock older than X minutes (by default, older than 5 minutes). Number of Object Locks older than X minutes is the number of locks in monitoring view M_OBJECT_LOCKS that have acquisition time older than X minutes. This default 'X' value can be changed with the collector's parameter LOCK_COUNT_OLDER_X_MINUTES) Locks are set on HANA objects to guarantee data integrity. It can happen that a lock remains too long (due to bug or bad design) and this will impact users (waiting for lock to be removed) and operation (too many cleanup file or many threads). Monitoring view M_OBJECT_LOCKS provides the status of currently acquired locks on objects with detailed information such as lock acquisition time or lock mode. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_OBJECTLOCK | HDB_5MIN | 5 Minutes |
| HDB_PARAM_CH | Number of changed HANA parameters | count | HANA | This KPI displays the number of changes in .ini file contents. If any parameter has been changed since the last run of the collector's execution, it counts this parameter to this KPI value. Additional details about the changed parameter values (old and new values) can be found in detail table 'HANA changed parameters'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_PAR | HDB_5MIN | 5 Minutes |
| HDB_PART_CNT_ABX | Number or partitions above X million rows | count | HANA | This KPI calculates the number of partitions which have more then X million rows. You might define this X-value with the collector's parameter 'PART_CNT_ABOVE_ROWS'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_1DAY | 1 Day |
| HDB_PCACHE_EVICD | SQL Plan Cache Eviction Delta (max all host) | count | HANA | This KPI displays the maximum change of Plan Eviction detected on all host since the last collector's execution. | Central system | System | any server | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 Minutes |
| HDB_PCACHE_EVICH | SQL Plan Cache Eviction per host | count | HANA | This KPI displays how many times Plan Eviction occurred on the specific host. If Plan Cache Eviction is too high, it means SQL plan cache capacity is not enough and too many compilations occurs. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 Minutes |
| HDB_PCACHE_EVIDH | SQL Plan Cache Eviction Delta per host | count | HANA | This KPI displays the changes of Plan Eviction on the specific host since the last run of the collector's execution. | Central system | Server | only database server | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 Minutes |
| HDB_PCACHE_HR_SR | SQL Plan Cache Hit Ratio per host | % | HANA | This KPI displays SQL Plan Cache Hit Ratio per host. The hit ratio is the percentage of pages found in the cache without any reads from the disk. The ratio shows the average percentage of data pages found in the cache since SQL Server was started. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 Minutes |
| HDB_PLANCACHE_HR | Min. SQL Plan Cache Hit Ratio (all hosts) | % | HANA | This KPIs displays the minimal SQL Plan Cache Hit Ratio from all hosts. The hit ratio is the percentage of pages found in the cache without any reads from the disk. The ratio shows the average percentage of data pages found in the cache since SQL Server was started. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 Minutes |
| HDB_REP_DELAY | System replication: Log shipping delay | s | HANA | Log shipping delay occurred during the system replication from primary to secondary site. Check for errors or communication issues that can be responsible for the log shipping delays and make sure that log can be shipped in time. See SAP note 1999880 - FAQ: SAP HANA System Replication | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_REP_ERROR | Number of system replication errors | count | HANA | This KPI calculates the number of errors during system replication between primary and secondary site. Analyze the related trace files in order to understand the reason for the problems and make sure that system replication is again established. See SAP note 1999880 - FAQ: SAP HANA System Replication | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_REP_SS_AGE | Age of oldest replication snapshot | min | HANA | This KPI displays the age of the oldest replication snapshot. Database snapshots can increase the data disk space requirements and so you should make sure that system replication related snapshots are not kept longer than necessary. The snapshot retention time is controlled by the following parameter: global.ini -> [system_replication] -> datashipping_snapshot_max_retention_time. See SAP note 1999880 - FAQ: SAP HANA System Replication | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_REP_UNKNOWN | Number of unknown replication statuses | count | HANA | This KPI displays the number of unknown replication statuses during system replication between primary and secondary site. Analyze the related trace files in order to understand the reason for the problems and make sure that system replication is again established. See SAP note 1999880 - FAQ: SAP HANA System Replication | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_RS_ALLOC | Row store allocated size | MB | HANA | This KPI displays the allocated size of row store. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_RS_FRAG | Row store fragmentation | % | HANA | Row store grows by allocating a 64MB memory segment and shrinks by freeing empty segments. A segment is internally divided into fixed-size pages. When a row store table requires more memory to store records, the table takes a free page from existing segments. If no segment has a free page, a new segment is allocated. Deleting a large number of records may result in a number of sparse segments. In such a case, row store reorganization can be performed for memory compaction. The pages in sparse segments are moved to other segments and the resultant empty segments are freed. If row store fragmentation exceeds 30%, row store reorganization is recommended. See SAP Note 1813245 - SAP HANA DB: Row store reorganization. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 Minutes |
| HDB_SP_COUNT | Number of save points | count | HANA | This KPI displays the number of save points. During a save point, the database system writes the data which has changed since the last save point from the data cache (working memory) to the data area (permanent storage). The data written during a save point always represents a consistent state of the database. During a save point the database system does not overwrite the pages written to the data area at the previous save point, but instead writes the changed data to free positions. This is because the database system requires this information from the previous save point for a restart if there is a system failure during the new save point. Only after the database system has successfully completed the new save point does it release the pages of the old save point in the data area for overwriting. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 Minutes |
| HDB_SP_LAST | Time since last save point | s | HANA | Save points in HANA database are responsible for synchronization of memory pages with disks, which is necessary for system recovery. The frequency of save points is defined using parameter global.ini -> [persistence] -> savepoint_interval_s. If this KPI exceeds the interval significantly, it means save point was not successful and there is a synchronization issue. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 Minutes |
| HDB_SP_MAXRUN | Max. duration of save point | s | HANA | This KPI displays maximal duration of save point. During a save point, the database system writes the data which has changed since the last save point from the data cache (working memory) to the data area (permanent storage). The data written during a save point always represents a consistent state of the database. During a save point the database system does not overwrite the pages written to the data area at the previous save point, but instead writes the changed data to free positions. This is because the database system requires this information from the previous save point for a restart if there is a system failure during the new save point. Only after the database system has successfully completed the new save point does it release the pages of the old save point in the data area for overwriting. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 Minutes |
| HDB_SP_MAXRUN_C | Max. critical phase duration of a save point | s | HANA | This KPI displays the maximum critical phase duration of a save point. During a save point, the database system writes the data which has changed since the last save point from the data cache (working memory) to the data area (permanent storage). The data written during a save point always represents a consistent state of the database. During a save point the database system does not overwrite the pages written to the data area at the previous save point, but instead writes the changed data to free positions. This is because the database system requires this information from the previous save point for a restart if there is a system failure during the new save point. Only after the database system has successfully completed the new save point does it release the pages of the old save point in the data area for overwriting. To perform a save point write operation, SAP HANA needs to take a global database lock. This period is called the critical phase of a save point. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 Minutes |
| HDB_SP_SPEED | Save point speed | MB/s | HANA | This KPI displays the speed of save point. During a save point, the database system writes the data which has changed since the last save point from the data cache (working memory) to the data area (permanent storage). The data written during a save point always represents a consistent state of the database. During a save point the database system does not overwrite the pages written to the data area at the previous save point, but instead writes the changed data to free positions. This is because the database system requires this information from the previous save point for a restart if there is a system failure during the new save point. Only after the database system has successfully completed the new save point does it release the pages of the old save point in the data area for overwriting. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 Minutes |
| HDB_SQL_EXP_STMT_DUR_NUM | Number of expensive SQL statements exceeding the time limit | count | HANA | This KPI calculates the number of SQL statements that take longer than time limit (by default longer than 100 ms). You might change this time limit with collector's parameter 'TIME_DURATION_LIMIT_IN_MS'). If you see this KPI reaching value of 100 more frequently, you might change this value with collector's parameter 'TOP_RECORDS' to higher value. You might find additional details about expensive SQL statements in detail table 'HANA expensive statements'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SQL_STMT | HDB_5MIN | 5 Minutes |
| HDB_SQL_EXP_STMT_NUM | Number of expensive statements exceeding the memory limit | count | HANA | This KPI calculates the number of expensive SQL statements whose peak memory size exceeds the configured threshold during their execution (by default more then 500 MB). You might change this memory limit with collector's parameter 'MEMORY_SIZE_LIMIT_IN_MB'. If you see this KPI is reaching value of 100 more frequently, you might change this value with collector's parameter 'TOP_RECORDS' to higher value. You might find additional details about expensive SQL statements in detail table 'HANA expensive statements'. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_SQL_STMT | HDB_5MIN | 5 Minutes |
| HDB_SRV_RESTART | Number of restarted index services | count | HDB_HA | Restart of an index server can indicate a node failover or another crash situation. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 Minutes |
| HDB_THR_BACKUP | Max. duration of Backup threads | s | HANA | This KPI displays the maximum duration of backup threads. A backup, or the process of backing up, refers to the copying and archiving of data so it may be used to restore the original after a data loss event. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_COUNT | Number of active HANA threads | count | HANA | This KPI displays the number of active threads which exists in HANA. The SAP NetWeaver Application Server provides logical services for processing the workload mapped through operation system processes. These include the dispatcher and work processes of the ABAP server, which are each implemented on UNIX derivatives as separate operating system processes and on Windows operating systems through what are known as threads within a process. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_JOBWRUN | Thread JobWorker Running (max all hosts) | count | HANA | This KPI calculates the maximum number of running JobWorker threads from all hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_JOBWRUNH | Thread JobWorker Running per host | count | HANA | This KPI calculates the total number of running JobWorker threads per each host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_JOBWTTL | Thread JobWorker Total (max all hosts) | count | HANA | This KPI calculates the maximum number of JobWorker threads from all hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | ||
| HDB_THR_JOBWTTLH | Thread JobWorker Total per host | count | HANA | This KPI calculates the total number of JobWorker threads per each host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_MAXRUN | Max. duration of HANA threads | s | HANA | This KPI displays the maximum duration of all running HANA threads. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_MC_CPUT | MemoryCompactor CPU Time - ratio per sec (max all host) | % | HANA | This KPI displays the maximum ratio between the delta CPU time of the thread and number of seconds between 2 snapshots on each host. It’s a number of parallel threads that are processed by MemoryCompactor (also called incorrectly Garbage Collector). When "defragmentation" / thread MemoryCompactor is running, ERP is slow and can be extremely slow as defragmentation requires a IPMM lock (it can create locks on NRIV or other critical tables). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_MC_CPUTH | MemoryCompactor CPU Time (ratio per sec) per host | % | HANA | This KPI displays the ratio between the delta CPU time of the thread and number of seconds between 2 snapshots on each host. It’s a number of parallel threads that are processed by MemoryCompactor (also called incorrectly Garbage Collector). When "defragmentation" / thread MemoryCompactor is running, ERP is slow and can be extremely slow as defragmentation requires a IPMM lock (it can create locks on NRIV or other critical tables). | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_MERGEDOG | Max. duration of MergeDog threads | s | HANA | This KPI displays the maximal duration of MergeDog threads. A system process called MergeDog periodically checks the to the storage server and for which auto merge is enabled. It then determines for each individual table (or single partition of a split storage) if a merge should be executed based on configurable criteria. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_REPLICA | Maximum runtime of replications | s | HANA | This KPI displays the time taken for replicating the data from primary site to secondary. Long time of replication is always after the back up (it can be co-related with the KPI Max. duration of backup thread). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SAMPLE | Number of HANA Thread samples | count | HANA | This KPI calculates the number of all running HANA Thread samples. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THR_SAMPLE | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLEC1 | Number of Thread SqlExecutor (running more than 1 minute) | count | HANA | This KPI displays the number of all Thread SqlExecutor which are running more than 1 minute on any host. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLERUN | Number of running Thread SqlExecutor (max all hosts) | count | HANA | This KPI displays the maximum number of running Thread SqlExecutor from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLERUNH | Number of running Thread SqlExecutor per host | count | HANA | This KPI displays the number of running Thread SqlExecutor per each host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLETTL | Total number of Thread SqlExecutor (max all hosts) | count | HANA | This KPI displays the maximum number of Thread SqlExecutor from all available hosts. | Central system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLETTLH | Total number of Thread SqlExecutor per host | count | HANA | This KPI displays the total number of Thread SqlExecutor per each host. | Remote system | Server | only database server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_SQLRUN | Max. duration of SqlExecutor threads | s | HANA | This KPI displays the maximal duration of SqlExecutor threads. These thread types handle incoming client requests and execute simple statements. For each statement execution, an SqlExecutor thread from a thread pool processes the statement. For simple (OLTP-like) statements against column store as well as for most statements against row store, this will be the only type of thread involved. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_THR_TIME_CAP | Runtime to capture threads | ms | HANA | This KPI displays the runtime to read all thread data from HANA monitoring view. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 Minutes |
| HDB_TRAN_BLOCK_C | Number of blocked transactions | count | HANA | This KPI displays the number of blocked transactions. Blocked transactions are transactions that are unable to be processed further, because they need to acquire transactional locks (record or table locks) ,that are currently held by another transaction. Transactions can also be blocked waiting for other resources such as network or disk (database or metadata locks).You can lock and unlock transaction codes in SM01. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 Minutes |
| HDB_TRAN_BLOCK_T | Duration of longest transaction lock wait | min | HANA | Some transactions are waiting too long for a DB lock (most probably some long-running program didn't release a lock using DB commit and blocks other transactions). | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 Minutes |
| HDB_TRAN_REDO | Maximum redo size of current transaction | MB | HANA | Every change in a database is written to log files. At commit time a database is closing a transaction and has to guarantee the log is written to disk. The logs can be used for recovery activities, DR sites, and crash recoveries. Too large transactions can heavily impact the system in case of rollbacks, and with long crash recovery or failover times. Most transactions are ideally below 1 GB. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 Minutes |
| HDB_TRAN_UNDO | Maximum undo size of current transaction | MB | HANA | Every transaction which changes data writes UNDO logs, which are used in case of process termination to rollback the changes. After the DB commit, the UNDO log is deleted. If this size is growing too much, it means there is changes are not committed often enough. Check if you can reduce the amount of performed change operations or if you can increase the COMMIT frequency in order to split the change load into several smaller pieces. | Remote system | System | any server | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 Minutes |
| HEAP_DIA | Dialog heap memory (server) | MB | SAPSYS | This KPI represents the amount of heap memory (Private Memory) that an SAP dialog work process can allocate on application server. Official parameter for this KPI is abap/heap_area_dia. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_NONDIA | Non-dialog heap memory (server) | MB | SAPSYS | This KPI represents the amount of heap memory ( Private Memory) that an SAP non-dialog work process can allocate on application server. This value refers to spool, update, and background processes. Official parameter of this KPI is abap/heap_area_nondia. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_TOTAL | Heap memory available (server) | MB | SAPSYS | This KPI represents total size of heap memory assigned for application server. This value contains dialog and non-dialog heap memory sizes combined. Official parameter of this KPI is abap/heap_area_total. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_DIA | Dialog heap memory used (server) | MB | SAPSYS | This KPI value represents how much of dialog heap memory is used in specific time for application server. Only dialog work processes can use this private memory. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_DIA_P | Percentage of used dialog heap memory (server) | % | SAPSYS | This KPI value represents the percentage of how much of dialog heap memory is used in specific time for application server. Only dialog work processes can use this private memory. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_DIA_P_SYS_MAX | Maximum of used dialog heap memory (all servers) | % | SAPSYS | This KPI value represents the percentage of used dialog heap memory across all application servers. | Central system | System | any server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_NONDIA | Non-dialog heap memory used (server) | MB | SAPSYS | This KPI value represents how much of non-dialog heap memory is used in specific time for application server. Only non-dialog work processes can use this private memory. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_NONDIA_P | Percentage of used non-dialog heap memory (server) | % | SAPSYS | This KPI value represents the percentage of how much of non-dialog heap memory is used in specific time for application server. Only non-dialog work processes can use this private memory. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_NONDIA_P_SYS_MAX | Maximum of used non-dialog heap memory (all servers) | % | SAPSYS | This KPI value represents the percentage of used non-dialog heap memory across all application servers. | Central system | System | any server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_TOTAL | Heap memory used (server) | MB | SAPSYS | This KPI represents total size of allocated heap memory in time for application server. KPI defines how much of total heap is used with dialog and non-dialog work processes combined. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_TOTAL_P | Percentage of used heap memory (server) | % | SAPSYS | This KPI represents the percentage of total size for allocated heap memory in time for application server. KPI defines how much of total heap is used with dialog and non-dialog work processes combined. | Remote system | Server | only application server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| HEAP_USED_TOTAL_P_SYS_MAX | Maximum of used heap memory (all servers) | % | SAPSYS | This KPI value represents the percentage of used total heap memory (dialog + non-dialog) across all application servers. | Central system | System | any server | /DVD/MON_CL_COL_HEAP | DEF_5MIN | 5 Minutes |
| ICM_CURR_CONN | Current connections count (server) | count | SAPSYS | KPI value represents total number of currently used connections to the application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_CURR_QUE | Number of current entries in queue (server) | count | SAPSYS | KPI value represents how many entries are currently in request queue. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_CURR_THR | Number of all threads (server) | count | SAPSYS | This KPI represents the number of all available threads on application server. This contains threads either in running/idle/completed state. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_IDLE_THR | Number of idle threads (server) | count | SAPSYS | KPI value represents the number of running threads that are in idle state on application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_MAX_CONN | Maximum limit for allowed connections (server) | count | SAPSYS | KPI value represents how many connections can be maintained by application server at the same time. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_MAX_QUE | Maximum limit for allowed entries in request queue (server) | count | SAPSYS | KPI value represents the maximum limit of how many entries can be in request queue at one moment. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_MAX_THR | Maximum limit for allowed threads (server) | count | SAPSYS | Maximum allowed threads on application server at one time. Application server may sometimes override limit if it needs to. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_PEAK_CONN | All time peak connections (server) | count | SAPSYS | KPI value represents the maximum connections set on the application server in specific time. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_PEAK_QUE | All time peak entries in request queue (server) | count | SAPSYS | KPI value represents all-time maximum entries in queue for one given moment. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_PEAK_THR | All time peak threads (server) | count | SAPSYS | All time peak thread count. Specifies all-time maximum number of threads that were active at the same time. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_RUNN_THR | Number of running threads (server) | count | SAPSYS | KPI value represents the number of threads, that are in "Running" state on application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_RUN_THR_P | Percentage of used running threads (server) | % | SAPSYS | KPI value represents the percentage of threads used (RUNNING state) in given point of time (running threads/all threads). If this value is e.g. 20% - that means rest (80%) are threads in IDLE state or occasionally in UNKNOWN if SAP can't determine its state. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_UNK_THR | Number of threads in unknown state (server) | count | SAPSYS | KPI value represents the number of threads that are currently in "Unknown" state on application server (in case of some error or unknown cause). | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_USED_CONN_P | Percentage of used connections (server) | % | SAPSYS | KPI value represents the percentage of connections used (current connections/max allowed connections). Application server may have large amount of connections allowed and only few of them used - values below 1% of usage are reported as 0%. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_USED_QUE_P | Percentage of used request queues (server) | % | SAPSYS | KPI value represents the percentage of used queues (current entries/max allowed entries). | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| ICM_USED_THR_P | Percentage of used available threads (server) | % | SAPSYS | KPI value represents the percentage of how many threads are available at one time compared to maximum allowed threads on application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_ICM | DEF_5MIN | 5 Minutes |
| IDOCS_CHANGED | Number of IDocs changed or created in last period | count | IDOC | This KPI calculates the number of all changed or created IDocs in last snapshot period. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_DETAIL | IDOC_1HOUR | 1 Hour |
| IDOC_INBOUND_C | Total number of Inbound IDocs for last snapshot | count | IDOC | This KPI calculates the total number of Inbound IDocs for the last snapshot of the collector's execution. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_IN_ERRORS | Number of errors in Inbound IDocs processing | count | IDOC | This KPI displays the number of errors in Inbound IDocs processing. List of IDoc Inbound statuses indicating error and are counted to this KPI: 51 - Posting error, 52 - Posting error, 54 - Error during formal application check, 56 - IDOC with error added, 60 - Syntax error, 61 - Processing despite syntax error, 63 - Error passing IDOC to application, 65 - ALE error. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_I_PROC_AVG | Average time of successful inbound IDoc processing (50-53) | s | IDOC | This KPI calculates the average time of all successful Inbound IDoc processing (50-53) for the last snapshot. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_OUTBOUND_C | Total number of Outbound IDocs for last snapshot | count | IDOC | This KPI calculates the total number of Outbound IDocs for the last snapshot of the collector's execution. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_OUT_ERRORS | Number of errors in Outbound IDocs processing | count | IDOC | This KPI displays the number of errors in Outbound IDocs processing. List of Outbound IDoc statuses indicating error and are counted to this KPI: 02 - Error passing data to port, 04 - Control information of EDI subsystem, 05 - Translation , 07 - Syntax check, 09 - Interchange handling, 11 - Dispatch, 15 - Interchange acknowledgement negative, 17 - Functional acknowledgement negative, 20 - Triggering EDI subsystem, 23 - Retransmission, 25 - Processing despite syntax error, 27 - ALE error, 34 - Error in control record of IDOC, 36 - Timeout error; electronic signature not performed, 37 - IDOC added incorrectly, 40 - Application document not created in target system. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_O_PROC_AVG | Average time of successful outbound IDoc processing (01-30) | s | IDOC | This KPI calculates the average time of all successful Outbound IDoc processing (01-30) for the last snapshot. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| IDOC_O_TRANS_AVG | Average time of successful transmission (03->12) | s | IDOC | This KPI calculates the average time of all successful transmission from status 03 to status 12 for Outbound IDoc processing. | Remote system | System | any server | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 Hour |
| LAN_ERROR_IN | Number of Network errors In (server) | count | OS | This KPI displays the number of network errors In on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_ERROR_IN_SYS_SUM | Total number of Network errors In (all servers) | count | OS | This KPI displays the total number of network errors In for all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_ERROR_OUT | Number of Network errors Out (server) | count | OS | This KPI displays the number of network errors Out on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_ERROR_OUT_SYS_SUM | Total number of network errors Out (all servers) | count | OS | This KPI displays the total number of network errors Out for all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_PACKETS_IN | Number of Network packets In (server) | count | OS | This KPI displays the number of network packets In on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_PACKETS_IN_SYS_SUM | Total number of network packets In (all servers) | count | OS | This KPI displays the total number of network packets In for all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_PACKETS_OUT | Number of Network packets Out (server) | count | OS | This KPI displays the number of network packets Out on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LAN_PACKETS_OUT_SYS_SUM | Total number of network packets Out (all servers) | count | OS | This KPI displays the total number of network packets Out for all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| LOCK_LONGEST_DURATION | Duration of the longest Lock entry | hours | SAPSYS | This KPI calculates the longest duration of an existing lock entry in hours from all current lock entries in SM12 based on configured custom rules. By default, when no custom rule defined in input table /DVD/MON_LOCK_I, all locks are considered. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_ALL | Number of all existing Lock entries | number | SAPSYS | This KPI represents the number of all existing Lock entries on the system. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_ALL_SPECIFIC | Number of all existing Lock entries specified in Inputs | number | SAPSYS | This KPI represents the number of all existing Lock entries which are monitored by custom rules specified in input table /DVD/MON_LOCK_I. By default, when no rule defined in this input table, all locks are counted to this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_LONG_RUNNING | Number of specific Lock entries exceeding the time limit | number | SAPSYS | This KPI calculates the number of Lock entries which duration time is exceeding the configured time limit in minutes. By default, when no custom rule is specified in input table /DVD/MON_LOCK_I, default rule is automatically used with time limit for 10 minutes. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_MODE_E | Number of Exclusive locks (Lock mode E) | number | SAPSYS | This KPI calculates the number of Exclusive locks available in SM12 (Lock mode E) based on configured custom rules. By default, when no custom rule defined in input table /DVD/MON_LOCK_I, all Exclusive locks (E) are included into this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_MODE_O | Number of Optimistic locks (Lock mode O) | number | SAPSYS | This KPI calculates the number of Optimistic locks available in SM12 (Lock mode O) based on configured custom rules. By default, when no custom rule defined in input table /DVD/MON_LOCK_I, all Optimistic locks (O) are included into this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_MODE_S | Number of Shared locks (Lock mode S) | number | SAPSYS | This KPI calculates the number of Shared locks available in SM12 (Lock mode S) based on configured custom rules. By default, when no custom rule defined in input table /DVD/MON_LOCK_I, all Shared locks (S) are included into this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| LOCK_NUM_MODE_X | Number of Exclusive not cumulative locks (Lock mode X) | number | SAPSYS | This KPI calculates the number of Exclusive not cumulative locks available in SM12 (Lock mode X) based on configured custom rules. By default, when no custom rule defined in input table /DVD/MON_LOCK_I, all Exclusive not cumulative locks (X) are included into this KPI value. | Remote system | System | any server | /DVD/MON_CL_COL_LOCKS | DEF_5MIN | 5 Minutes |
| MEM_FREE | Memory free (server) | kB | OS | This KPI displays the free memory on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| MEM_FREE_SUM | Total free memory in system (all servers) | kB | OS | This KPI displays the total free memory in system on all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| MEM_PHYS | Physical memory available (server) | kB | OS | This KPI displays the available physical memory on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 Day |
| MEM_USED_P | Memory used (server) | % | OS | This KPI displays the used memory on the server. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| MEM_USED_P_SYS_MAX | Maximum of used memory (all servers) | % | OS | This KPI displays the maximum used memory from all servers. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| NR_MAX_DIFF | Maximum from incremental difference of all number ranges | count | SAPSYS | This KPI displays the maximum difference found in single monitored number range. | Remote system | System | any server | /DVD/MON_CL_COL_NUM_RANGE | DEF_1DAY | 1 Day |
| NR_MAX_SPEED | Maximum from incremental speed of number ranges | val/d | SAPSYS | This KPI displays the maximum speed found in single monitored number range. | Remote system | System | any server | /DVD/MON_CL_COL_NUM_RANGE | DEF_1DAY | 1 Day |
| NR_OVER_THR | Number of number ranges which are over threshold | count | SAPSYS | This KPI calculates the number of all number ranges that are over threshold. Does not matter if it is speed, difference or percentage threshold (default value for each threshold can be viewed in collector's parameters). | Remote system | System | any server | /DVD/MON_CL_COL_NUM_RANGE | DEF_1DAY | 1 Day |
| NR_TOTAL_DIFF | Sum of all incremental differences of number ranges | count | SAPSYS | This KPI displays the differences of all monitored number ranges summed into one value. | Remote system | System | any server | /DVD/MON_CL_COL_NUM_RANGE | DEF_1DAY | 1 Day |
| NR_TOTAL_SPEED | Sum of all speeds of monitored number ranges | val/d | SAPSYS | This KPI displays the total speed of all monitored number ranges. This value represents how fast are numbers assigned from number ranges by day. | Remote system | System | any server | /DVD/MON_CL_COL_NUM_RANGE | DEF_1DAY | 1 Day |
| ORA_CPU_IDLE | Oracle: CPU idle | % | ORACLE | Times in which the CPU had no task to perform or was waiting for an input/output. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_CPU_UTIL | ORA_5MIN | 5 Minutes |
| ORA_CPU_NICE | Oracle: CPU used by priority jobs | % | ORACLE | This KPI displays the percentage usage of CPU used by priority jobs on Oracle. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_CPU_UTIL | ORA_5MIN | 5 Minutes |
| ORA_CPU_SYS | Oracle: CPU used by system | % | ORACLE | This KPI displays the percentage usage of CPU used by system on Oracle. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_CPU_UTIL | ORA_5MIN | 5 Minutes |
| ORA_CPU_USER | Oracle: CPU used by user | % | ORACLE | This KPI displays the CPU used by user on Oracle (details can be checked in transaction ST06). | Remote system | System | any server | /DVD/MON_ORA_CL_COL_CPU_UTIL | ORA_5MIN | 5 Minutes |
| ORA_CPU_WAIT | Oracle: CPU IO Wait | % | ORACLE | 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 capture for the database and for all application servers. This KPI displays only the worst value (usually IO wait of the database, IO wait on AS is usually zero). | Remote system | System | any server | /DVD/MON_ORA_CL_COL_CPU_UTIL | ORA_5MIN | 5 Minutes |
| ORA_LOG_00060 | ORA-00060 - Deadlock detected while waiting for resource | count | ORACLE | This KPI displays the number of errors identified in the alert logs with ID 'ORA-00060' - Deadlock detected while waiting for resource. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 Minutes |
| ORA_LOG_01578 | ORA-01578 - Data block corrupted | count | ORACLE | This KPI displays the number of errors identified in the alert logs with ID 'ORA-01578' - Data block corrupted. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 Minutes |
| ORA_LOG_01653 | ORA-01653 - Unable to extend table *.* by * in tablespace * | count | ORACLE | This KPI displays the number of errors identified in the alert logs with ID 'ORA-01653' - Unable to extend table *.* by * in tablespace *. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 Minutes |
| ORA_LOG_27072 | ORA-27072 - File I/O error | count | ORACLE | This KPI displays the number of errors identified in the alert logs with ID 'ORA-27072' - File I/O error. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 Minutes |
| ORA_LOG_30036 | ORA-30036 - Unable to extend segm. by * in undo tab.sp. '*' | count | ORACLE | This KPI displays the number of errors identified in the alert logs with ID 'ORA-30036' - Unable to extend segm. by * in undo tab.sp. '*'. | Remote system | System | any server | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 Minutes |
| ORA_MEM_BUFFER_CACHE | Oracle: Buffer cache size | MB | ORACLE | This KPI displays the buffer cache size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_FREE | Oracle: Free memory size | MB | ORACLE | This KPI displays the free memory size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_FREE_P | Oracle: Free memory | % | ORACLE | This KPI displays the percentage of free memory on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_JAVA_POOL | Oracle: Java Pool Size | MB | ORACLE | This KPI displays the Java Pool Size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_LARGE_POOL | Oracle: Large Pool Size | MB | ORACLE | This KPI displays the Large Pool Size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_SHARED_POOL | Oracle: Shared Pool Size | MB | ORACLE | This KPI displays the Shared Pool Size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_TOTAL | Oracle: Total memory size | MB | ORACLE | This KPI displays the total memory size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_TOTAL_PGA_ALLOCATED | Oracle: Total PGA allocated size | MB | ORACLE | This KPI displays the total PGA allocated size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_USED | Oracle: Used memory size | MB | ORACLE | This KPI displays the used memory size in MB on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_MEM_USED_P | Oracle: Used memory | % | ORACLE | This KPI displays the percentage of used memory on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_PGA_USED | Oracle: Total PGA memory used size | MB | ORACLE | This KPI displays the size of PGA Memory used on Oracle database. | Remote system | Server | any server | /DVD/MON_ORA_CL_COL_MEM | ORA_5MIN | 5 Minutes |
| ORA_SESS_ALL | Number of all active and blocking Oracle sessions | count | ORACLE | This KPI calculates the number of active or blocking Oracle user sessions where background tasks (command value is not equal to 0) are excluded. Details are collected into Detail Table "ORACLE active sessions". | Remote system | System | any server | /DVD/MON_ORA_CL_COL_SESSION | ORA_5MIN | 5 Minutes |
| ORA_SESS_COMMIT | Number of currently committing Oracle sessions | count | ORACLE | This KPI calculates the number of Oracle sessions which currently committing (an indicator of slowness in the area of DB logging). In case of increased counters, check wait states and I/O statistics for DB logging. Details are collected into Detail table "ORACLE active sessions". | Remote system | System | any server | /DVD/MON_ORA_CL_COL_SESSION | ORA_5MIN | 5 Minutes |
| ORA_SESS_ENQWAIT | Number of Oracle sessions waiting for enqueue | count | ORACLE | This KPI calculates the number of sessions waiting for Oracle Enqueue (typically lock-wait). In case of lock-wait, identify applications with columns SID and BLOCKING_SESSION in the detail table involved in the blocked situation. Details are collected into Detail table "ORACLE active sessions". | Remote system | System | any server | /DVD/MON_ORA_CL_COL_SESSION | ORA_5MIN | 5 Minutes |
| ORA_SESS_INST | Number of active and blocking Oracle sessions per host | count | ORACLE | This KPI calculates the number of active or blocking Oracle user sessions per each host where background tasks (command value is not equal to 0) are excluded. Details are collected into Detail table "ORACLE active sessions". | Remote system | Server | only external server | /DVD/MON_ORA_CL_COL_SESSION | ORA_5MIN | 5 Minutes |
| OS_RUN_PS_COUNT | Get number of running processes on OS | count | OS | This KPI displays the number of running processes on OS. This KPI serves as an example based on which you might define custom KPIs for any OS command. | Remote system | System | any server | /DVD/MON_CL_COL_SYS_CMD | N/A - need to schedule this KPI manually* | Custom |
| PAGE_IN | Pages IN in kB/s | kB/s | OS | This KPI displays the value for Pages IN from memory per hour. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PAGE_IN_P | Pages IN from memory per hour (server) | % | OS | This KPI displays the percentage of pages in per hour for each server. The memory utilization statistics are important to ensure that system performance is running smoothly. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PAGE_IN_P_SYS_MAX | Maximum of memory Pages IN per hour (all servers) | % | OS | This KPI displays the maximum percentage of memory page IN per hour from all servers. The memory utilization statistics are important to ensure that system performance is running smoothly. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PAGE_OUT | Pages OUT in kB/s | kB/s | OS | When not null, it indicates that system is swapping. CCMS calculates page out in kb by sec. The value is converted per hour (multiplied by 3600) then divided by total physical memory available on the hardware to calculate the value in percentage. Values are capture for the database and for all application servers. However the chart will display only the worst value. You can see page out in kb per sec in SAP with OS07. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PAGE_OUT_P | Pages OUT from memory per hour (server) | % | OS | The memory utilization statistics are important to ensure that system performance is running smoothly. This KPI displays the number of pages out per hour. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PAGE_OUT_P_SYS_MAX | Maximum of memory Pages OUT per hour (all servers) | % | OS | The memory utilization statistics are important to ensure that system performance is running smoothly. This KPI displays the maximum number of pages out per hour from all servers. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| PARAM_CHANGED | Number of changed system profile parameters | count | SAPSYS | This KPI displays the number of changed profile parameters. Parameters can be changed in transaction RZ11 and some changes can affect security or performance of system. Additional details about changed parameters can be found in detail table 'Changed profile parameters (App. server)'. | Remote system | System | any server | /DVD/MON_CL_COL_PARAM | DEF_1DAY | 1 Day |
| PI_CHANNELS_ERROR | Number of Error PI channels | count | JAVAPI | This KPI displays the total number of PI channels which are in the error state. Additional details for PI Error channels can be found in detail table 'PI error messages'. | Remote system | System | any server | /DVD/MON_CL_COL_PI_CHANNELS | PI_JAVA_5M | 5 Minutes |
| PI_CHANNELS_OK | Number of OK PI channels | count | JAVAPI | This KPI displays the total number of PI channels which are in the OK state. | Remote system | System | any server | /DVD/MON_CL_COL_PI_CHANNELS | PI_JAVA_5M | 5 Minutes |
| PI_CHANNELS_STOPPED | Number of Stopped PI channels | count | JAVAPI | This KPI displays the total number of PI channels which are in the stopped state. | Remote system | System | any server | /DVD/MON_CL_COL_PI_CHANNELS | PI_JAVA_5M | 5 Minutes |
| PI_MESSAGES_CANCEL | Number of canceled PI Messages | count | JAVAPI | This KPI displays the number of PI Messages in canceled state since last run of the collector's execution. | Remote system | System | any server | /DVD/MON_CL_COL_PI_MESSAGE | PI_JAVA_5M | 5 Minutes |
| PI_MESSAGES_ERROR | Number of error PI messages | count | JAVAPI | This KPI displays the number of PI Messages in error state since last run of the collector's execution. | Remote system | System | any server | /DVD/MON_CL_COL_PI_MESSAGE | PI_JAVA_5M | 5 Minutes |
| PI_MESSAGES_SUCCESS | Number of successful PI messages | count | JAVAPI | This KPI displays the number of PI Messages in successful state since last run of the collector's execution. | Remote system | System | any server | /DVD/MON_CL_COL_PI_MESSAGE | PI_JAVA_5M | 5 Minutes |
| PI_MESSAGES_TIME_WAITING | Time of longest scheduled PI message | s | JAVAPI | This KPI displays the longest time of scheduled PI Message. | Remote system | System | any server | /DVD/MON_CL_COL_PI_MESSAGE | PI_JAVA_5M | 5 Minutes |
| PI_MESSAGES_WAITING | Number of waiting PI messages | count | JAVAPI | This KPI displays the number of PI Messages in waiting state since last run of the collector's execution. | Remote system | System | any server | /DVD/MON_CL_COL_PI_MESSAGE | PI_JAVA_5M | 5 Minutes |
| PI_MSG_ALL | Number of all PI status messages | count | SAPSYS | This KPI calculates the number of all PI (eXchage Infrastructure/Process Integration/Process Orchestration) messages collected from SXI_MONITOR. PI messages provide details about traffic flow that passes through a PI system. Value greater than zero means that traffic is passing through the PI system. | Remote system | System | any server | /DVD/MON_PI_CL_COL_MSG | PI_5MIN | 5 Minutes |
| PI_MSG_ERROR | Number of PI error messages | count | SAPSYS | This KPI calculates the number of failed PI (eXchage Infrastructure/Process Integration/Process Orchestration) messages collected from SXI_MONITOR. PI messages provide details about traffic flow that passes through a PI system. Value greater than zero means that there are issuesin traffic that passes through the PI system. Detail table "PI status messages" - /DVD/MON_PI_D1 contains detail records for each collected failed PI message. Number of PI messages that ended with an error status: 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 | 5 Minutes |
| QRFC_ERR_IN | Number of erroneous inbound qRFC queues | number | SAPSYS | Number of erroneous inbound qRFC queues on all clients with state different as RUNNING and READY. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| QRFC_ERR_OUT | Number of erroneous outbound qRFC queues | number | SAPSYS | Number of erroneous outbound qRFC queues on all clients with state SYSFAIL. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| QRFC_IN | Number of all entries for inbound qRFC queues | number | SAPSYS | Number of all entries from table TRFCQIN for inbound qRFC queues on all clients. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| QRFC_OUT | Number of all entries for outbound qRFC queues | number | SAPSYS | Number of all entries from table TRFCQOUT for outbound qRFC queues on all clients. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| QRFC_QIN_COUNT | Number of Inbound qRFC queues | number | SAPSYS | Number of Inbound qRFC queues on all clients. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| QRFC_QOUT_COUNT | Number of Outbound qRFC queues | number | SAPSYS | Number of Outbound qRFC queues on all clients. | Remote system | System | any server | /DVD/MON_CL_COL_QRFC | DEF_5MIN | 5 Minutes |
| RFC_CIF_IN_15 | tRFCqIN number of entries Queue CIF older than 15minutes | count | SAPSYS | This KPI shows tRFCqIN number of entries Queue CIF 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 need to be rectified as soon as possible, before they lead to serialization effects. To do this, you have to be able to display the contents of the queues in such a way that the object that caused the error can be determined as quickly as possible and any necessary changes can be made. CIF queue display enables you to do this. tRFCqIN is a standard SAP Table which is used to store tRFC Queue Description (Inbound Queue) information. The relevant SAP transaction for viewing this information is SE11 or SE80. The viewing data contained in this database table via these transactions or alternatively use transaction SE16. | Remote system | System | any server | /DVD/MON_CL_COL_RFCQ | DEF_1HOUR | 1 Hour |
| RFC_CIF_OUT_15 | tRFCqOUT number of entries Queue CIF older than 15minutes | count | SAPSYS | This KPI shows tRFCqOUT number of entries Queue CIF 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 need to be rectified as soon as possible, before they lead to serialization effects. To do this, you have to be able to display the contents of the queues in such a way that the object that caused the error can be determined as quickly as possible and any necessary changes can be made. CIF queue display enables you to do this. tRFCqOUT is a standard SAP Table which is used to store tRFC Queue Description (Outbound Queue) information. The relevant SAP transaction for viewing this information is SE11 or SE80. The viewing data contained in this database table via these transactions or alternatively use transaction SE16. | Remote system | System | any server | /DVD/MON_CL_COL_RFCQ | DEF_1HOUR | 1 Hour |
| RFC_IN_AUTHERR | Number of failed RFC tests - RFC check with authorization | count | SAPSYS | Count of failed Authorization Test. Authorization Test provides complete RFC test with authorization and calling of functional module. Value greater than zero means that something is wrong. Check detailed table contains the list of failed RFC destinations with name: "Details for unsuccessful RFC connection tests" - /DVD/MON_S_RFC_DETAILS | Remote system | System | any server | /DVD/MON_CL_COL_RFC | DEF_1HOUR | 1 Hour |
| RFC_IN_CON_ERR | Number of failed RFC tests - RFC check without authorization | count | SAPSYS | Count of failed Connection Test. Connection Test checks if there is available and running requested SAP system. Value greater than zero means that something is wrong. Check detailed table contains the list of failed RFC destinations with name: "Details for unsuccessful RFC connection tests" - /DVD/MON_S_RFC_DETAILS | Remote system | System | any server | /DVD/MON_CL_COL_RFC | DEF_1HOUR | 1 Hour |
| RFC_IN_PINGERR | Number of failed RFC tests - ping server IP | count | SAPSYS | Count of failed Ping Test. This test pings the IP defined in RFC, this only tests if the server with RFC connection is reachable. Value greater than zero means that something is wrong. Check detailed table contains the list of failed RFC destinations with name: "Details for unsuccessful RFC connection tests" - /DVD/MON_S_RFC_DETAILS | Remote system | System | any server | /DVD/MON_CL_COL_RFC | DEF_1HOUR | 1 Hour |
| ROLL_USED_P | Roll area used | % | OS | This KPI displays the amount of Roll area used. In the Roll area is stored the user context data, such as user authorizations, Set/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 Extended Memory is full or because the user quota has been reached. | Remote system | Server | only application server | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 Minutes |
| ROLL_USED_P_SYS_MAX | Maximum of roll area used (all servers) | % | OS | This KPI displays the maximum amount of Roll area used from all servers. In the Roll area is stored the user context data, such as user authorizations, Set/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 Extended Memory is full or because the user quota has been reached. | Central system | System | any server | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 Minutes |
| SDTR_ERROR_CNT | Number of all transmissions in error status | count | SAPSYS | This KPI displays the number of all transmission records in error state. | Remote system | System | any server | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 Hour |
| SDTR_TRANSMT_CNT | Number of successfully transmitted mail requests | count | SAPSYS | This KPI displays the number of all transmission records in delivered or send state. | Remote system | System | any server | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 Hour |
| SDTR_WAITING_CNT | Number of all waiting transmissions | count | SAPSYS | This KPI displays the number of all transmission records which are in waiting state (waiting, inconsistent or in future). | Remote system | System | any server | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 Hour |
| SERVER_IS_DOWN | Server is down (true = 1 / false = 0 ) | COL | OS | KPI for server accessibility check. First RFC ping is done to check availability, then OS ping is done. Value 1 means server was checked and is not accessible. Value 0 means that server is running. | Central system | Server | any server | /DVD/MON_CL_COL_SYSTEM | DEF_1MIN | 1 Minute |
| SERVER_IS_DOWN_SYS_SUM | Number of not reachable servers | number | OS | This KPI displays the number of all not reachable servers for the system (RFC and OS ping fails) | Central system | System | any server | /DVD/MON_CL_COL_SYSTEM | DEF_1MIN | 1 Minute |
| SERVER_RFC_FAIL | Server unreachable via RFC (true = 1 / false = 0) | bool | OS | KPI similar to SERVER_IS_DOWN KPI but is more sensitive. Value 1 means that server cannot be reached and is returned if RFC ping fails. OS ping is not used in this KPI. Value 0 corresponds to successful RFC ping. This KPI has no collector assigned. | Central system | Server | any server | /DVD/MON_CL_COL_SYSTEM | DEF_1MIN | 1 Minute |
| SERVER_RFC_FAIL_SYS_SUM | Number of not responding servers | number | OS | This KPI displays the number of all not responding servers for the system (RFC ping for server fails). | Central system | System | any server | /DVD/MON_CL_COL_SYSTEM | DEF_1MIN | 1 Minute |
| SLG_DEBUG | Number of changes in debug mode | count | SAPSYS | When user jump to debug mode of any application (either run in background or called via http) and will change some value in runtime or change program flow logic then such change is recorded to system log. This KPI detect such record in system log. Value of KPI represent number of findings from last snapshot. Details about each finding is stored in detail table of collector. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SLG_KERNEL | Number of activated C-calls debugging | count | SAPSYS | When user jump to debug mode of any C-call in runtime then it is recorded to system log. This KPI detect such record in system log. Value of KPI represent number of findings from last snapshot. Details about each finding is stored in detail table of collector. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SLG_PRIO_HIGH | Number of HIGH priority messages in the system log | count | SAPSYS | This KPI displays the number of messages in the system logs with HIGH priority. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SLG_PRIO_INFORMATION | Number of INFORMATION messages in the system log | count | SAPSYS | This KPI displays the number of messages in the system logs with INFORMATION priority. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SLG_PRIO_VERY_HIGH | Number of VERY HIGH priority messages in the system log | count | SAPSYS | This KPI displays the number of messages in the system logs with VERY HIGH priority. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SLG_PRIO_WARNING | Number of WARNING messages in the system log | count | SAPSYS | This KPI displays the number of messages in the system logs with WARNING priority. | Remote system | System | any server | /DVD/MON_CL_COL_SYSLOG | DEF_1HOUR | 1 Hour |
| SSL_CERT_EXP | Number of expiring certificates | count | SAPSYS | Total number of currently expiring/expired SSL certificates across STRUST identities. Certificate is marked as expiring if it has less than 10% of lifetime left and at the same time expiring in less days than defined by parameter (default 30 days). | Remote system | System | any server | /DVD/MON_CL_COL_SSL_CERT | DEF_1DAY | 1 Day |
| STAD_INBOUND_RFC_COUNT | Number of all inbound RFC (APPD STAD MAIN) | count | STAT | This KPI displays the number of all inbound RFC where additional details about workload statistics can be found in detail tables 'Workload statistics RFC' and 'Workload statistics transaction jobs'. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_WORKLOAD | DEF_5MIN | 5 Minues |
| STAT_DB_DIALOG_AVG | Average Response Time for Users on Database | ms | STAT | This KPI displays the average database time from statistical SAP transactions (Tx STAD/ST03) for dialog tasks. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_DB_RESP_AVG | Average Response Time on Database | ms | STAT | This KPI displays the average database time from statistical SAP transactions (Tx STAD/ST03) for all tasks. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_DIALOG_AVG | Average System Response Time for Users | ms | STAT | Average time between the time at which a dialog process sends a request to a dispatcher work process and the time at which the dialog is complete and the data is transferred to the presentation layer. The response time does not include the time for transferring the data from the SAP front end to the application server. Networks with bad performance can therefore have larger subjective response times. The transfer time is included in the GUI time and the front end network time. Average system response time is usually time around 1 second(dialog) < 1 second (update). This KPI shows this time, which is adequate for users. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_DIALOG_TOT | Total System Response Time for Users | ms | STAT | This KPI displays the total system response time for users. The response time of a transaction step is the difference between the time when the request arrives in the R/3 system and the time when processing in the R/3 system is complete. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_M_RESP_BC | [BC] Response time from Basis Components | ms | STAT | This KPI displays the response time from Basis Components. The SAP BC (Basis Components) is the root of the SAP Applications ERP software. It provides the runtime environment for the rest of the R/3 Applications. It ensures that applications are optimally integrated in the system environment. The SAP Basis Components contains powerful tools such as CCMS (Computing Center Management System) for easy system administration. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_M_RESP_BW | [BW] Response time from SAP Business Inf. Warehouse | ms | STAT | This KPI displays the response time from SAP Business Inf. Warehouse. As a core component of SAP NetWeaver, the SAP Business Information Warehouse (SAP BW) provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools that enable businesses to attain these goals. Relevant business information from productive SAP applications and all external data sources can be integrated, transformed and consolidated in SAP BW with the toolset provided. SAP BW provides flexible reporting and analysis tools to support you in evaluating and interpreting data, as well as facilitating its distribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_M_RESP_XXXX | Total response time from undefined components | ms | STAT | This KPI displays the total response time from components which are undefined. The response time of a transaction step is the difference between the time when the request arrives in the R/3 system and the time when processing in the R/3 system is complete. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_M_TCNT_BC | [BC] Number of trans. from Basis Components | count | STAT | This KPI displays the number of transactions from Basis Components. The SAP BC (Basis Components) is the root of the SAP Applications ERP software. It provides the runtime environment for the rest of the R/3 Applications. It ensures that applications are optimally integrated in the system environment. The SAP Basis Components contains powerful tools such as CCMS (Computing Center Management System) for easy system administration. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_M_TCNT_BW | [BW] Number of trans. from SAP Business Inf. Warehouse | count | STAT | This KPI displays the number of transactions from SAP Business Inf. Warehouse. As a core component of SAP NetWeaver, the SAP Business Information Warehouse (SAP BW) provides data warehousing functionality, a business intelligence platform, and a suite of business intelligence tools that enable businesses to attain these goals. Relevant business information from productive SAP applications and all external data sources can be integrated, transformed, and consolidated in SAP BW with the toolset provided. SAP BW provides flexible reporting and analysis tools to support you in evaluating and interpreting data, as well as facilitating its distribution. Businesses are able to make well-founded decisions and determine target-orientated activities on the basis of this analysis. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_M_TCNT_XXXX | Number of transactions from undefined components | count | STAT | This KPI displays the number of transactions from undefined components. | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 Hour |
| STAT_RSA1_AVG | Average Response Time of transaction RSA1 | ms | STAT | This KPI displays the average response time of transaction RSA1 (SE16 - Modeling - DW Workbench). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_SE16_AVG | Average Response Time of transaction SE16 | ms | STAT | This KPI displays the average response time of transaction SE16 (SE16 - Data Browser). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_SE16_CNT | Number of SE16 transaction starts | count | STAT | This KPI displays the number of SE16 transaction starts (SE16 - Data Browser). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_SE16_TTL | Response Time of transaction SE16 | ms | STAT | This KPI displays the response time of transaction SE16 (SE16 - Data Browser). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_SE38_RESP | Response Time of transaction SE38 | ms | STAT | This KPI displays the response time of transaction SE38 (SE38 - ABAP Editor). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| STAT_SE38_RUN | Average Runtime of reports running via SE38 | ms | STAT | This KPI displays the average Runtime of reports running via transaction SE38 (SE38 - ABAP Editor). | Remote system | System | any server | /DVD/MON_STAT_CL_COL_MODULES | DEF_5MIN | 5 Minutes |
| SWAP_CONF | Swap configured space | kB | OS | This KPI displays the amount of configured swap space. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 Day |
| SWAP_DELTA | Delta between previous and current used swap | kB | OS | This is the difference between 2 snapshots of Free Swap in percentage of total swap. This is more accurate that Page Out % which is a snapshot when FM runs. It's possible that the system was paging 1 minute before the FM runs and page out returns 0. But it takes some time to recover from paging and delta swap will show a value. 0.5% of delta swap is already too much. | Central system | Server | only application server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_DELTA_P | Delta between previous and current used swap | % | OS | This is the difference between 2 snapshots of used swap in percentage of total swap. This is more accurate that Page Out % which is a snapshot when collector runs. It is possible that the system was paging 1 minute before the collector runs and page out returns 0. But it takes some time to recover from paging and delta swap will show a value. | Central system | Server | only application server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_DELTA_PMAX | Delta between swap (max all servers) | % | OS | Swap used is calculated by CCMS, see transaction ST06N. This KPI is the delta of the swap used between the last 2 snapshots, calculated in percentage of swap area. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_FREE | Free swap space | kB | OS | This KPI displays the free Swap space in percentage of total swap. When it reaches zero, the instance is dead. When going down it means the system is swapping. But swap are more accurate in indicator Page Out %, as free swap is a HWM. Values are captured for all servers (AS and BD), the minimum value is displayed in the chart. You can see this with OS07. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_USED | Used swap space | kB | OS | This KPI displays the amount of used swap space (in kB). | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_USED_P | Used swap space | % | OS | KPI calculates percentages of used swap space by substituting actual value SWAP_FREE from SWAP_CONF. | Remote system | Server | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SWAP_USED_PMAX | Used swap (max all servers) | % | OS | Swap used is calculated by CCMS, see transaction ST06N. This KPI is the max swap used in percentage of swap area for all servers monitored for this SID. | Central system | System | any server | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 Minutes |
| SYSTEM_IS_DOWN | System is not responding (true = 1 / false = 0 ) | bool | SAPSYS | Special KPI hardcoded in CrystalBridge® Monitoring without collector assignment. Value 1 represents the state when system is not responding (not able to reach the satellite system via RFC call). This KPI might be used for alerting about system availability. | Central system | System | any server | /DVD/MON_CL_COL_SYSTEM | DEF_1MIN | 1 Minute |
| TOP_INDEX_SIZE_TOTAL | Total index size for top largest tables | MB | SAPSYS | Total index size in MB for the largest tables on the system. By default, into this KPI value are calculated the index sizes for top 50 largest tables. The total number of processed tables might be changed in the collector's parameter TOP_N_TABLES. You might also set the minimal table size threshold in the parameter MIN_TABLE_SIZE_THRESHOLD_MB. When value for MIN_TABLE_SIZE_THRESHOLD_MB defined, only tables with table size greater than this value will be processed. Additional details for each table can be found in detail table "Details for Table size statistics". | Remote system | System | any server | /DVD/MON_CL_COL_TAB_SIZE | DEF_1DAY | 1 Day |
| TOP_TABLE_SIZE_TOTAL | Total table size for top largest tables | MB | SAPSYS | Total table size in MB for the largest tables on the system. By default, into this KPI value are calculated the table sizes for top 50 largest tables. The total number of processed tables might be changed in the collector's parameter TOP_N_TABLES. You might also set the minimal table size threshold in the parameter MIN_TABLE_SIZE_THRESHOLD_MB. When value for MIN_TABLE_SIZE_THRESHOLD_MB defined, only tables with table size greater than this value will be processed. Additional details for each table can be found in detail table "Details for Table size statistics". | Remote system | System | any server | /DVD/MON_CL_COL_TAB_SIZE | DEF_1DAY | 1 Day |
| UPD_REQ_CANCEL | Number of cancelled Update requests | count | SAPSYS | An update request, or update record, describes the data changes determined in an SAP LUW. These changes should be made completely, or not all (this means, in a database LUW). This refers only to V1 updates. V2 updates are triggered once the V1 update is complete and are processed in a separate database LUW. An update request is identified by its update key. An update request consists of an update header, V1 modules (or components), V2 module and a collective run module. When the update requests are canceled, this situation is displayed by this KPI. | Remote system | System | any server | /DVD/MON_CL_COL_UPD_REQ | DEF_1HOUR | 1 Hour |
| UPD_REQ_TOBEUPD | Update requests to be updated | count | SAPSYS | An update request, or update record, describes the data changes determined in an SAP LUW. These changes should be made completely, or not all (this means, in a database LUW). This refers only to V1 updates. V2 updates are triggered once the V1 update is complete, and are processed in a separate database LUW. An update request is identified by its update key. An update request consists of an update header, V1 modules(or components), V2 module and collective run module. This KPI shows situation, when update requests to be updated. | Remote system | System | any server | /DVD/MON_CL_COL_UPD_REQ | DEF_1HOUR | 1 Hour |
| USER_CNT | Number of active users | count | SAPSYS | This KPI displays the number of active users. | Remote system | System | any server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_CNT_SER | Number of active users (server) | count | SAPSYS | This KPI displays the number of active users on specific application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_EXT_MOD | Number of external modes | count | SAPSYS | This KPI displays the number of external modes. | Remote system | System | any server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_EXT_MOD_SER | Number of external modes (server) | count | SAPSYS | This KPI displays the number of external modes on specific application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_GUI_CNT | Number of interactive users | count | SAPSYS | This KPI displays the number of interactive users. | Remote system | System | any server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_GUI_CNT_SER | Number of interactive users (server) | count | SAPSYS | This KPI displays the number of interactive users on specific application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_INT_MOD | Number of internal modes | count | SAPSYS | This KPI displays the number of internal modes. . | Remote system | System | any server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_INT_MOD_SER | Number of internal modes (server) | count | SAPSYS | This KPI displays the number of internal modes on specific application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_RFC_CNT | Number of RFC-users | count | SAPSYS | This KPI displays the number of RFC-users. | Remote system | System | any server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USER_RFC_CNT_SER | Number of RFC-users (server) | count | SAPSYS | This KPI displays the number of RFC-users on specific application server. | Remote system | Server | only application server | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 Minutes |
USR_INIT | Number of users never logged in | count | SAPSYS | The number of SAP users with never logged in. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_INIT_PW | Number of users with initial password | count | SAPSYS | The number of SAP users with initial passwords and logged time. Indicating that password is probably reset. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_INVALID | Number of expired users | count | SAPSYS | The number of SAP users which past their validity date. Only applicable to users created with specified VALID_TO date. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_LOCK | Number of locked users | count | SAPSYS | The number of locked SAP users on a system, irrespective of the lock reason. For example, they can be locked by administrator, too many failed login attempts or other reasons. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_OLD | Number of users with password age above preset threshold | count | SAPSYS | The number of SAP users that have a password older than configured by parameter OLD_PASSWORD. By default, it is set to 180 days, but can be changed in Collector settings under "Parameters" tree. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_SAPS_DEL | Number of deleted SAP* users on system (across all clients) | count | SAPSYS | The number of non-existing SAP* users on a system (across all clients). Removed SAP* users are a potential security risk, as they can be used as backdoor login. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
USR_SAPS_KER | Security risk with SAP* user | bool | SAPSYS | A Flag that indicates an imminent security risk on a system. Value 1 is returned, if the SAP* user is removed on any client and a kernel login using SAP* is permitted. Related is profile parameter login/no_automatic_user_sapstar. | Remote system | System | any server | /DVD/MON_CL_COL_USR | DEF_1DAY | 1 Day |
WDISP_CONN_USED_CURR | Number of currently used connection | count | WDISP | Number of currently used connections in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_CONN_USED_MAX | Maximum number of used connection | count | WDISP | Maximum number of used connections in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_IS_RUNNING | Is Admin Web Interface running? | bool | WDISP | This KPI represents whether the Administration Interface for Web Dispatcher is running or not ("1-running", "0-not running). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_QUEUE_USED_CURR | Number of currently used Queue entries | count | WDISP | Number of currently used Queue entries in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_QUEUE_USED_MAX | Maximum number for used Queue entries | count | WDISP | Maximum number of used Queue entries in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_STATUS | Web Admin Interface Status (1-running, 2-maintenance) | status | WDISP | This KPI represents the status in which is the Administration Interface for Web Dispatcher ("1-running", "2-maintenance"). If the Administration Interface for Web Dispatcher is not running, this KPI value is not collected. | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_THRD_CREATED_CURR | Number of currently created threads | count | WDISP | Number of currently created threads in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_THRD_CREATED_MAX | Maximum number for created threads | count | WDISP | Maximum number for created threads in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_THRD_IDLE | Number of threads in Idle state | count | WDISP | Number of threads with status 'idle' in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WDISP_THRD_RUNNING | Number of currently running threads | count | WDISP | Number of threads with status 'running' in SAP Web Dispatcher Monitor (Web Dispatcher Administration Interface). | Remote system | System | any server | /DVD/MON_WDISP_CL_COLLECTOR | WDISP_5MIN | 5 Minutes |
WP_BTC_CONF | Number of BTC configured (server) | count | SAPSYS | Number of free BTC WP (for the instance) divided by total number of BTC WP. When it reaches zero, batch jobs are queuing. You can see total / free BTC WP in SAP with transaction SM66. Some charts display Used BTC % = 100 % - Free BTC %. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 Hour |
WP_BTC_CONF_SUM | Number of BTC configured (all servers) | count | SAPSYS | Number of free BTC WP (for the instance) divided by total number of BTC WP. When it reaches zero, batch jobs are queuing. You can see total / free BTC WP in SAP with transaction SM66. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 Hour |
WP_BTC_USED | Number of used BTC (server) | count | SAPSYS | This KPI counts number of used BTC work processes on the server. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_BTC_USED_MAX | Usage of BTC (max all servers) | % | SAPSYS | KPI value determines number of BTC work processes (WP) of server with the highest amount of BTC WP - returns value of the busiest server. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_BTC_USED_P | Usage of BTC (server) | % | SAPSYS | Number of used BTC WP (for the instance) divided by total number of BTC WP. When it reaches 100%, batch jobs are queuing. You can see total / free BTC WP in SAP with transaction SM66. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_BTC_USED_SUM | Number of used BTC (all servers) | count | SAPSYS | Number of used DIA work processes captured in SM66 for all application servers (saved in /DVD/MON_WPINFO on the central instance). | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_BTC_USED_S_P | Usage of BTC (all servers) | % | SAPSYS | For the WP info we calculate the number of batch work processes (BTC WP) currently used for the system (SID), in percentage of total number of BTC WP configured for this system. It?s not looking at a specific application server but calculated for the sum of all application server. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_COMMIT | Number of WP in COMMIT state | count | SAPSYS | This KPI counts the number of work processes currently in COMMIT state. The captured state of Tx SM66 is saved in the detailed table "Work Process Info". | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_CONF | Number of DIA configured (server) | count | SAPSYS | This KPI displays the number of DIA work processes configured on the server. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 Hour |
WP_DIA_CONF_SUM | Number of DIA configured (all servers) | count | SAPSYS | This KPI displays the number of DIA work processes configured on all servers. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 Hour |
WP_DIA_LONGR | Longest running DIA WP (server) | s | SAPSYS | This KPI displays the longest running DIA work process (in seconds). | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_LONGR_MAX | Longest running DIA WP (max all servers) | s | SAPSYS | Maximum runtime of DIA WP captured in SM66 (saved in /DVD/MON_WPINFO on the central instance). | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_NBR_AT | Number of long running DIA WP (server) | count | SAPSYS | Adjusted value of Average response DIA (sec) excluding DIA WP from users RFC-* and DIA WP with duration greater than timeout, so the indicator adjusted will display only when several users have response time of several minutes. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_NBR_ATDU | Number of long running DIA WP for Dialog User (server) | count | SAPSYS | This KPI is dependent is on parameters configured in the configure file, specifically the on parameter DIA_THRESHOLD_DIALOG_USER. It returns number of dialog WP which duration is longer then the predetermined value by parameter. The default value is 120 seconds. Value can be changed in collector parameters setup. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_NBR_ATDUS | Number of long running DIA WP for Dialog User (all servers) | count | SAPSYS | This KPI is dependent is on parameters configured in the configure file, specifically the on parameter DIA_THRESHOLD_DIALOG_USER. It counts the number of all dialog WP from all servers which duration is longer then the predetermined value by parameter. The default value is 120 seconds. Value can be changed in collector parameters setup. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_NBR_ATSUM | Number of long running DIA WP (all servers) | count | SAPSYS | A snapshot of SM66 is taken every 5 minutes (saved in /DVD/MON_WPINFO on the central instance). This KPI is the number of DIA WP running for more than 120sec that are in the captured sm66. The threshold (120sec) can be changed in the parameters of the collector /DVD/MON_CL_COL_GET_WP. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_RT_AVG | Avg. runtime of DIA processes (server) | s | SAPSYS | Average response time of dialog WP captured in SM66. The exact value is meaningless, but the trend is important and when increasing it can show a lock-wait situation or few WP that are not killed after timeout. Values are capture for all application servers. The chart displays the average for the instance. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_RT_AVG_A | Avg. runtime of DIA processes (all servers) | s | SAPSYS | Average response time of dialog WP captured in SM66. The exact value is meaningless, but the trend is important and when increasing it can show a lock-wait situation or few WP that are not killed after timeout. Values are capture for all application servers. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_USED | Number of used DIA (server) | count | SAPSYS | This KPI counts number of used dialog WP on server. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_USED_MAX | Number of used DIA (max all servers) | % | SAPSYS | Max value of number of DIA WP used per server in percentage of total number of DIA WP in the same server. When all DIA are used on an application server, the users connected on this server could have connection issue, even if some DIA WP are available on other application servers. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_USED_P | Usage of DIA (server) | % | SAPSYS | Number of free DIA WP (for the instance) divided by total number of DIA WP. You can see total/free DIA WP in SAP with transaction SM66. When it reaches zero, the server looks frozen for many users. The trend shows if more of less PW are running. To be compare to CPU load: If CPU load increases dramatically and number of WP is stable, it show bad behavior, unless CPU load goes above 80%. Some charts display Used DIA% = 100% - Free DIA %. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_USED_SUM | Number of used DIA (all servers) | count | SAPSYS | Number of used DIA work processes captured in SM66 for all application servers (saved in /DVD/MON_WPINFO on the central instance). | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_DIA_USED_S_P | Usage of DIA (all servers) | % | SAPSYS | The percentage of work process usage for dialog. Calculation: number of used DIA WP (for the instance) divided by total number of DIA WP. Work process Information (e.g. SM66) is captured every 5 minutes. This KPI is calculated for the sum of all application servers. When it reaches 100%, users may experience waits and slowness in transactions. The trend shows if more of less WP are running. To be compare to CPU load: If CPU load increases dramatically and number of WP is stable, it shows expensive ABAP behavior. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_MAX_REPORT | Number of WP on same report (all servers) | count | SAPSYS | Number of work processes (DIA or BTC) on the same report captured in sm66(saved in /DVD/MON_WPINFO on the central instance), for all users. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_MAX_TABLE | Number of WP on same table (all servers) | count | SAPSYS | Count the number of work processes (DIA or BTC) on the same table name, captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for all users. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_MAX_USER | Number of WP with the same user (all servers) | count | SAPSYS | Number of work processes (DIA or BTC) with the same user captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for user type Dialog user. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_NRIV | Number of WP accessing number ranges | count | SAPSYS | Number of WP captured in sm66 (saved in /DVD/MON_WPINFO on the central instance) showing table = NRIV. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_SAPLSENA | Number of WP calling ENQUEUE | count | SAPSYS | This KPI displays the number of WP running report SAPLSENA in captured sm66 (saved in /DVD/MON_WPINFO on the central instance). Those are processing enqueues. If too many ENQ are raised at the same time, or if processing of ENQ is slow, we have seen hundreds WP hanging in SAPLSENA. Eventually all WP can be used and the complete system will be hanging. When there are many ENQ, the DIA will take longer, see the chart below showing the correlation between the No. of DIA WP running for more than 120secand the number of WP in SAPLSENA. | Remote system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_UP2_CONF | Number of UP2 configured (server) | count | SAPSYS | This KPI is number of configured work processes for task processing on server - these tasks are in update process with the priority V2. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 Day |
WP_UP2_CONF_SUM | Number of UP2 configured (all servers) | count | SAPSYS | This KPI is number of configured work processes for task processing on all servers - these tasks are in update process with the priority V2. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 Day |
WP_UP2_USED | Number of used UP2 (server) | count | SAPSYS | UP2 is used for 'statistical' updates (and some RFC signaling). Number of used UP2 WP (for the instance) divided by total number of UP2 WP. When it reaches 100%, all transactions are stopped. You can see total / free UP2 WP in SAP with transaction SM66. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_UP2_USED_SUM | Number of used UP2 (all servers) | count | SAPSYS | UP2 is used for 'statistical' updates (and some RFC signaling).Number of used UP2 WP (for the instance) divided by total number of UP2 WP. When it reaches 100%, all transactions are stopped. You can see total / free UP2 WP in SAP with transaction SM66. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_UPD_CONF | Number of UPD configured (server) | count | SAPSYS | This KPI is number of configured work processes for task processing on server - these tasks are in update process with the highest priority (V1). | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 Day |
WP_UPD_CONF_SUM | Number of UPD configured (all servers) | count | SAPSYS | This KPI is number of configured work processes for task processing on all servers - these tasks are in update process with the highest priority (V1). | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 Day |
WP_UPD_USED | Number of used UPD (server) | count | SAPSYS | Number of used UPD WP (for the instance) divided by total number of UPD WP. When it reaches 100%, all transactions are stopped. You can see total / free UPD WP in SAP with transaction SM66. | Remote system | Server | only application server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WP_UPD_USED_SUM | Number of used UPD (all servers) | count | SAPSYS | Number of used UPD WP (for the instance) divided by total number of UPD WP. When it reaches 100%, all transactions are stopped. You can see total / free UPD WP in SAP with transaction SM66. | Central system | System | any server | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 Minutes |
WRONG_SUPPRESS_KEY_NUM | Number of systems with wrong suppress key | count | SAPSYS | KPI serves for detecting wrong suppress keys in system definition. Some monitored systems are marked by monitor as production either they are not (quality system or pre-production system). For such system a suppress key can be provided. If suppress key is not valid anymore the KPI value is increased and detail information is written to Monitor's self check messages. | Central system | System | any server | /DVD/MON_CL_COL_SELFCHECK | DEF_5MIN | 5 Minutes |
* N/A (need to schedule this KPI manually) - this KPI does not have any profile defined by default. If you want to monitor this KPI, you need to define a monitoring profile as described in (DI-2205) Define a Monitoring Profile for a KPI.