(DI-1708) Complete list of KPIs
| KPI | Description | Long description | Monitoring area | KPI area (collected for) | Server selection (Server specification) | Collected on | Collector | Profile | Recommended mon.period |
| ARFC_FREE | Number of available (free) WP for aRFC resources | SAPSYS | SYS | any server | Remote system | /DVD/MON_CL_COL_ARFC | 5 MI | ||
| ARFC_FREE_P | Percentage of available (free) WP for aRFC resources | SAPSYS | SYS | any server | Remote system | /DVD/MON_CL_COL_ARFC | DEF_5MIN | 5 MI | |
| ARFC_WAIT | Wait time of aRFC for free WP | SAPSYS | SYS | any server | Remote system | /DVD/MON_CL_COL_ARFC | |||
| BAT_DB_INSERT_AG | Average DB insert | Insertion is a process, where array insert of N entries from internal table. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. This KPI shows average database insert. | BENCH | SYS | application and database server | Central system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BAT_DB_INSERT_MS | DB Insertion benchmark | Insertion is a process, where array insert of N entries from internal table. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. Database insertion benchmark displays this KPI. | BENCH | SYS | application and database server | Remote system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BAT_DB_SELECT_AG | Average DB select | Select - with WHERE clause on primary key, such as to select all N entries. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. Database select and it's average is measured by KPI with name BAT_DB_SELECT_AG. | BENCH | SYS | application and database server | Central system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BAT_DB_SELECT_MS | DB Select bechmark | Select - with WHERE clause on primary key, such as to select all N entries. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. This KPI shows database select benchmark. | BENCH | SYS | application and database server | Remote system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BAT_DB_UPDATE_AG | Average DB update | Update - with WHERE clause on primary key, such as to update single non-key field on N entries. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. Process of average DB update is displayed by this KPI. | BENCH | SYS | application and database server | Central system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BAT_DB_UPDATE_MS | DB Update benchmark | Update - with WHERE clause on primary key, such as to update single non-key field on N entries. N is by default 10 000 entries, but can be changed with the parameter NUM_RECORDS of the collector /DVD/MON_BAT_CL_DB. Database update benchmark is processed this KPI. | BENCH | SYS | application and database server | Remote system | /DVD/MON_BAT_CL_DB | DEF_5MIN | 5 MI |
| BTC_NUM_DELAYED | Number of delayed background jobs ( => 60 seconds) | The kpi value represent a count of background jobs that waiting for free work process more then 60 seconds. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_BTC_CL_COL_JOBS | DEF_5MIN | 5 MI |
| BTC_NUM_FAILED | Number of failed background jobs | The kpi value represent a count of background jobs that failed. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_BTC_CL_COL_JOBS | DEF_5MIN | 5 MI |
| BTC_NUM_LONGRUN | Number of background jobs running too long ( >= 10 minutes) | The kpi value represent a count of background jobs that running more than 10 minutes. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_BTC_CL_COL_JOBS | DEF_5MIN | 5 MI |
| BW_12503CNT | Javastack: count number of 12503 | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CNT_NOTA | Javastack: count number of 12503 on not authorized node | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CXMN_AVG | Javastack: count number of 12503 Xminute-avg per node hourly | JAVAST | SYS | application and database server | Central system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CXMN_MAX | Javastack: count number of 12503 Xminute-maximum node hourly | JAVAST | SYS | application and database server | Central system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CXMN_MIN | Javastack: count number of 12503 Xminute-minimum node hourly | JAVAST | SYS | application and database server | Central system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CXMN_MNV | Javastack: count number of 12503 Xminute-variance min node | JAVAST | SYS | application and database server | Central system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503CXMN_MXV | Javastack: count number of 12503 Xminute-variance max node | JAVAST | SYS | application and database server | Central system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI | |
| BW_12503HEAPMAX | Javastack : Max value of heap for all nodes | There are 10 nodes per system BW, instead of capturing and storing the memory of each node, we capture the memory of the most loaded. If the value remains at 84%, the memory consumption is too high. Check event 12505 above. | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI |
| BW_12503MISSUSR | Javastack : No of users with 12502 without 12503 after x min | When a web template v7 starts, it creates an entry 12502 in rsddstat_olap. At the end it create entry 12503. If a template fails on javastack, there is a 12502 without 12503. There is a timeout after 15minutes so a javastack session cannot take more than 15 minutes. However a javastack session should take only few seconds to 1 minute as it’s a user tool (not batch). This indicators count how many users have sessions 12502 not followed by 12503 after 5 minutes, one the same node. For all the KPI on javastack, we need at least BW730SP8 and BI JAVA SP7 Patch 30. See oss note: <a href='https://service.sap.com/sap/support/notes/1069253'> Note 1069253 - BEx Web 7.x: Monitoring server node memory use in OLAP stats</a> | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI |
| BW_12505NO | Javastack : No of queries rejected (stat 12505) | When memory on javastack is above rsadmin threshold, javastack will reject the request from the user (the we template will not run) and instead it will create an entry in rsddstat_olap event 12505. This KPI should be zero. If there is an issue (eg GC stucked) on memory of the javastack, this KPI will be greater than zero. | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI |
| BW_12640NO | Javastack : No of javastack cache refresh (stat 12640) | Cache refresh is done at javastack restart (or forced manually to refresh rsadmin parameter but this should be expectionnal). If no manual refresh is done,this indicator counts the javastack restarts. | JAVAST | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_JAVAST_EVT | BW_5MIN | 5 MI |
| BW_9000DMMISS | Number of queries failing on DM (BWA, DB, HANA) | When a queries fails on datamanager (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’s a general issue that needs to be addresses and reoccurrence must be prevented. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BW_AGGR_USAGE | Aggregate usage | Every 5 minutes we calculate the number of aggregate hit by comparing rsddstataggrdir field "usage" per aggregate with the previous snapshop. 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 changerun and rollup. | BW | SYS | only application server | Remote system | /DVD/MON_BW_CL_COL_AGGR_USAGE | BW_5MIN | 5 MI |
| BW_D_IP_ABTHRS | Yesterday's Number of IP with more than X packets | 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 Infopackages" 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 | BW | SYS | only application server | Remote system | /DVD/MON_BW_CL_COL_GET_D_IP | BW_1DAY | 1 DA |
| BW_DURATTRIBCHAN | BW duration running attribute changerun | During changerun, many bw jobs are locked so it is important that the attribute changerun 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 iscalculated 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 (ie jobg 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 orconflicting loads). | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 MI |
| BW_DURCOMPRESS | BW duration of longest running cube compression | 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 MI |
| BW_DURDBINDEX | BW duration of longest running DB indexing | 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 inthe 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*. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_5MIN | 5 MI |
| BW_DURLOADING | BW duration of longest running DTP | This indicators shows the longest running DTP, ie the longuest 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, butin 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 HO |
| BW_DURLOADIP | BW duration of longest running InfoPackage | This indicators shows the longest running InfoPackage. 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 alertif there is a long running infopackage and take ABAP, SQL traces to investigate the performance of this infopackage. See table BW infopackages to see for the top N requests, the request number, number of packets, runtime, infopackage, datasource. Only infopackages 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 HO |
| BW_DURMDACTIVAT | BW duration of longest running MD activation | This indicator shows the longest running Master Data activation job during changerun, 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 HO |
| BW_DURODSACTIVAT | BW duration of longest running ODS activation | 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, lockwait, 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_BATCH | BW_1HOUR | 1 HO |
| BW_IP_MAX_PACKET | BW IP max number of packets (multiplied by number of target) | Infopackage 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 pakets 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’s always multiplied by the number oftargets.This indicators shows the highest number of packets (multiplied by the number of targets) in the running InfoPackages. 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 thisvalue 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 infopackages » 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, infopackage, infosource, source, datasource. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 HO |
| BW_NR_MAX_DIFF | Maximum from incremental diffrence of all number ranges | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 DA | |
| BW_NR_MAX_SPEED | Maximum from incremental speed of number ranges per day | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 DA | |
| BW_NR_OVER_THR | Count of number range which are over threshold | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 DA | |
| BW_NR_TOTAL_DIFF | Maximum from incremental diffrence of all number ranges | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 DA | |
| BW_NR_TOTAL_SPEE | Incremental speed from all number ranges per day | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_NUM_RANGE | BW_1DAY | 1 DA | |
| BW_PC_STEP_COUNT | BW PC step count | Number of steps that finished since the last execution of the agent. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_PC | BW_1HOUR | 1 HO |
| BW_PC_STEP_ERR | BW PC step error | 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). | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_PC | BW_1HOUR | 1 HO |
| BW_RSICCONT_GR12 | Forecast RSICCONT Growth in 12 months | The admin table RSICCONTcontains 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSICCONT | BW_1DAY | 1 DA |
| BW_RSICCONT_MX12 | Forecast RSICCONT Max number of entries per cube in 12months | 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 (see kpi definition "RSICCONT Growth in 12 months"). The current number of rows in RSICCONT plus the forecasted growth gives the forecasted number 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). | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSICCONT | BW_1DAY | 1 DA |
| BW_RSMONMESSPAC | BW Sum max number of packets for all running PSA | BW | SYS | any server | Remote system | /DVD/MON_BW_CL_COL_GET_IP | BW_1HOUR | 1 HO | |
| BW_SID_GR12 | Forecast SID Growth in 12 months | BW | SYS | only application server | Remote system | /DVD/MON_BW_CL_COL_SID_GROWTH | BW_1DAY | 1 DA | |
| BW_SID_MX12 | Forecast SID Max level in 12 months | BW | SYS | only application server | Remote system | /DVD/MON_BW_CL_COL_SID_GROWTH | BW_1DAY | 1 DA | |
| BW_SSQL_ALLNO | SQL-Total number of subqueries | Number of queries on the DB (infact running SQL statement, op mode 0) to correlate with performance issue if needed. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 HO |
| BW_SSQL_ALLTIM | SQL-Total time spent on subqueries | Cumulated time of all queries running on the DB (infact running SQL statement, op mode 0) to correlate with performance issue if needed. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 HO |
| BW_SSQL_SQAR | SQL-Average runtime of small subqueries | 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 HO |
| BW_SSQL_SQLO | SQL-No of small subqueries long running (eg > 10 SEC) | This KPI is the number of small queries running for more than 10sec. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 HO |
| BW_SSQL_SQNO | SQL-No of small subqueries | This KPI is the amount of small subqueries. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_1HOUR | 1 HO |
| BW_SUBQ_ALLNO | nonSQL-Total number of subqueries (BWA or HANA) | 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BW_SUBQ_ALLTIM | nonSQL-Total time spent on subqueries (BWA or HANA) | Cumulated time spent on BWA of all subqueries. Also to know if we are reaching some limit. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BW_SUBQ_SQAR | nonSQL-Average runtime of small subqueries (BWA or HANA) | 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BW_SUBQ_SQLO | nonSQL-No of small subqueries long running (eg>10SEC) eg BWA | See above the definition of small subqueries. 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. | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BW_SUBQ_SQNO | nonSQL-No of small subqueries (BWA or HANA) | This KPI is the amount of small subqueries (nonSQL). | BW | SYS | application and database server | Remote system | /DVD/MON_BW_CL_COL_RSDDSTATS | BW_5MIN | 5 MI |
| BWA_AGE_NEWSID | BWA : Age of oldest SID not processed | 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 : TCode SLG1, Filter : Object = "RSDDTREX" Subobject = "TAGGRFILL" Check that object is still active (table rsddbobjdir or transaction rsddb). We checked for the above in SLG1. every thing is fine. Hence we are closing the ticket. Please find the added attachment. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWASID | BWA_1HOUR | 1 HO |
| BWA_ALERT_RED_NO | BWA : Number of red alerts | This is a count of number of red alerts in TREXADMIN. The details of the alert can be seen in ‘Details’ tab, BWA Alerts. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 HO |
| BWA_CPU_USED | BWA : CPU load on most loaded blade | This KPI is the max cpu load (of all blades) calculated by TREXADMIN, FM TREX_EXT_LOAD_HISTORY since the last execution. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_INDX_INA_DUR | BWA : Missing or inactive bwa cube index - duration | 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, CanaryCode checks that all indexes exist and have status ACT. If an index is missing, CanaryCode flags the index as missing, calculate since when it’s missing and update the list that is visible from tab ‘Details’, "BWA inactive indexes".This kpi is the max missing period for all cubes. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 HO |
| BWA_INDX_INA_NO | BWA : Missing or inactive bwa cube index - number | 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’s 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. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 HO |
| BWA_IS_PING | BWA : IS Ping time | This kpi is the "ping" time calculated by TREXADMIN, FM TREX_EXT_LOAD_HISTORY field IS_PING_TIME, between the nameserver and the indexserver. The nameserver contacts each indexserver to check if the connection works fine. This KPI is the max value (of all blades) captured since the last execution. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_SERVICE_INAC | BWA : No of services inactive | 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’s visible only from time to time, so if CanaryCode reports that some services are inactive, filter status on active NE green and refresh regularly to see the status on TREX.But you can also see the service reported as inactive in the ‘Details’ tab,"BWA service restarted or inactive". | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_SERVICE_REST | BWA : No of services restarted | At each execution of the agent we check the "Start time" of each service in TREXADMIN. This kpi is the number of service restarted since the last execution. When the memory consumption of a blade exceed the limit, the blade might restart by itself. Whena 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. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_THRD_NO | BWA : Number of running threads for more than 10sec | 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 cube indexing, index merging, it is normal to have long runningthreads. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_THRD_TIME | BWA : Runtime of longuest thread | This is the runtime of the longest running thread captured in TREXADMIN. This kpi can inform when there is a lock, a zombie thread. If it does not cause any lock, an oss message should be open to investigate. If rollup or changerun or master data SID update is locked and must be solved immediately, then a restart of index server and rfc server is required. See doc on alerts. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 HO |
| BWA_TTLMEM | BWA : Memory on most loaded blade (as percentage of total) | The speed of a BWA system is limited by the speed of the slowest blade. If you have 15 blades, it’s important that you have memory available on all the blades. And 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 detailed for all the blades is saved in "Detail tab".This kpi is the max memory used of all blades calculated by TREXADMIN, FM TREX_EXT_LOAD_HISTORY since the last execution. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_TTLMEM_BL01 | BWA : Memory on Blade 1 | The most important kpi on memory is "BWA_TTLMEM BWA : Memory on most loaded blade (as percentage of total)". As it’s the most loaded blade, it will show different blade at different time. To see the trend on one blade, those kpi, memory on blade 1,2 and 3 are delivered. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_TTLMEM_BL02 | BWA : Memory on Blade 2 | The most important kpi on memory is "BWA_TTLMEM BWA : Memory on most loaded blade (as percentage of total)". As it’s the most loaded blade, it will show different blade at different time. To see the trend on one blade, those kpi, memory on blade 1,2 and 3 are delivered. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_TTLMEM_BL03 | BWA : Memory on Blade 3 | The most important kpi on memory is "BWA_TTLMEM BWA : Memory on most loaded blade (as percentage of total)". As it’s the most loaded blade, it will show different blade at different time. To see the trend on one blade, those kpi, memory on blade 1,2 and 3 are delivered. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_5MIN | 5 MI |
| BWA_UNLOADS | BWA : Unloads (max per blade) | This is the highest unload per blade reported by TREXADMIN (FM 'TREX_EXT_LOAD_HISTORY from field of structure 'TREX_LOAD_UNLOAD_COUNT') in the last 5 minutes. When the value KPI increases rapidly, it could indicate problems with memory or BWA owerload in worst case. The reason of this problem could be low memory or too big indexes. The count of unloads couldn't be bigger than 200 unloads in the last 24 hours. SAP NOTE 1796356 could be heplful for depth analysis. | BWA | SYS | application and database server | Remote system | /DVD/MON_BWA_CL_COL_BWA | BWA_1HOUR | 1 HO |
| CF_THRESHOLD | KPI with calculation function relative to threshold of KPI | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CA_CL_COL_CALC | |||
| CPU_IDLE | CPU true idle | Times in which the CPU had no task to perform or was waiting for an input/output. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_LOAD1 | CPU - Average processes waiting (1 min) | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs,this indicates that the CPU is reducing the overall performance of the system. "CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all applicationservers. The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue.But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_LOAD1_P | CPU - Average processes waiting (15 min) | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs,this indicates that the CPU is reducing the overall performance of the system. "CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all applicationservers. The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue. But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_LOAD15 | CPU - Average processes waiting (15 min) per CPU | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs,this indicates that the CPU is reducing the overall performance of the system. "CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all applicationservers. The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue.But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | 15 MI | |
| CPU_LOAD15_P | CPU - Average processes waiting (1 min) per CPU | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs,this indicates that the CPU is reducing the overall performance of the system."CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all application servers. The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue. But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | 15 MI | |
| CPU_LOAD5 | CPU - Average processes waiting (5 min) | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs,this indicates that the CPU is reducing the overall performance of the system. "CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all applicationservers. The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue.But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| CPU_LOAD5_P | CPU - Average processes waiting (5 min) per CPU | The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs, this indicates that the CPU is reducing the overall performance of the system."CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all applicationservers.The chart displays only the CPU of the database. There are many AS and CPU of AS is usually not an issue. But bad exec plan can increase dramatically CPU load of the DB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| CPU_LOAD5_PMAX | CPU - Maximum average processes waiting (5 min) per CPU | CPU_LOAD5_PMAX is the maximum value of CPU load in 5 minute across all servers. The Average CPU Load (1, 5, and 15 minute averages) is the average number of processes that are ready for execution, but which must wait for the CPU. In SAP, you can see this indicator with OS07. If the average number of processes waiting is higher than the number of available CPUs, this indicates that the CPU is reducing the overall performance of the system."CPU load %" is the CPU load divided by number of CPU available on the hardware. Values are capture for the database and for all application servers.The chart displays only the CPU of the database.There are many AS and CPU of AS is usually not an issue.But bad exec plan can increase dramatically CPU load of the DB. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| CPU_NBR | Number of CPU's | The number of CPU's is displayed by this KPI. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 DA |
| CPU_SYS | CPU used by system | Percentage usage of CPU by user is diplayed by this KPI. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_USER | CPU used by user | CPU used by user is measured by KPI with name CPU_USER and suitable transaction for checking is ST06. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_WAIT | CPU IO wait | 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). | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CPU_WAIT_MAX | CPU IO wait (max. in all servers) | 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. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| CTS_AGE_OLDESTRQ | CTS - Age of the oldest request in queue | Age of the oldest transport request in queue. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 DA |
| CTS_COUNT_REQNM | CTS - Number of requests not moving in queue | 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. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_CTS | DEF_1HOUR | 1 HO |
| CTS_RC0008 | CTS - Number of transport in RC8 | Number of transport request with RC8. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 DA |
| CTS_RC0008A | CTS - Number of transport in RC8 and above | Number of transport request with RC8 and above. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 DA |
| CTS_RC0012A | CTS - Number of transport in RC12 and above | Number of transport request with RC12 and above. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_CTS | DEF_1DAY | 1 DA |
| DB_CPU_LOAD5_P | DB CPU Load (avg 5 min) per CPU | The value is calculated by CCMS, see transaction ST06N, select the database. This KPI is the "cpu load avg 5 min" divided by the number of CPU. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB_CPULOAD | DEF_5MIN | 5 MI |
| DB_CRIT_TAB_SP_P | Free space on most critical data file (tablespace) | KPI displays percentage of free space that has most critical data file of database available. Most critical data file (table space) is chosen by size, so the biggest data file (table space) 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. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_5MIN | 5 MI |
| DB_FREE | Free size of database | KPI displays percentage of free space that has most critical data file of database available. Most critical data file (table space) is chosen by size, so the biggest data file (table space) 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. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_INDEX_NUM | Total number of indexes | This kpi contains informations about 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 | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_INDEX_SIZE | Total size of indexes | This kpi describe, how total size can be acquire indexes. Transaction, which find out total size of indexes is : DBACOCKPIT -> SPACE -> SEGMENTS -> OVERVIEW -> TOP SIZES (and then filter on column type). | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_SIZE | Size of database | Database size contains : 1. number of records in tables 2. Table columns and their sizes 3. Indexes in the model 4. Tablespaces in the model 5. DBMS and its storage options All these factors affect size of database and total summary of these elements is processed this kpi. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_TAB_NUM | Total numbers of tables | Each database has several tables. Table is one of basic database objects, which main role is storing data into memory space of relational database. This kpi measure how much tables contains database. Information about total numbers of tables contains transaction DB02. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_TAB_SIZE | Total size of 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. Displaying the table size : 1. Open the Database Assistant 2. Choose Statistics --> Table Size This KPI displays actual value of size all tables. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DB_USED | Used size of database | KPI of used DB size in MB. This KPI is calculated as total DB size minus DB free space available. Threshold values depend on DB system used and on company needs. | DB | SYS | application and database server | Remote system | /DVD/MON_CL_COL_DB | DEF_1DAY | 1 DA |
| DELAY_LAST_RUN | Delay since last successful run | 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. | SAPSYS | SYS | application and database server | Central system | DEF_1MIN | 1 MI | |
| DEQ_ALL_REQ_CNT | Number of releases of all locks of an LUW | 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. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| DEQ_ERROR_CNT | Number of errors that occurred when releasing locks | 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. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| DEQ_REQUEST_CNT | Number of release requests (DEQUEUE) | 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 transtaction. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| DISK_AVG_WAIT | Average disk wait (server) | This KPI is the average disk wait on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DISK_RESPONS_SYS | Disk response time (server) | This KPI is average disk response time on all servers. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DISK_RESPONSE | Average disk response time (all servers) | This KPI is disk response time on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DISK_UTIL | Disk utilization (server) | This KPI is disk utilization on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DISK_UTIL_SYS | Average disk utilization (all servers) | This KPI is disk utilization on all servers. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DISK_WAIT_SYS | Average disk wait time (all servers) | This KPI is average disk wait time on all servers. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| DUMP_AUTH_ERR | Number of dumps on authorization failure | This KPI represent a count of dump which occurred by missing authorization | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 HO |
| DUMP_DBIF | Number of dumps on SQL operations | This KPI represent a count of dump which occurred by SQL operations. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_DUMP | DEF_1HOUR | 1 HO |
| DUMP_NBR | Number of dumps on a server | Number of dumps for all application servers as per ST22 from last monitoring time. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 DA |
| DUMP_NBR_SUM | Number of dumps (all servers) | Number of dumps on the SID since the last run of CanaryCode. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 DA |
| DUMP_SYNTAX_ERR | Number of dumps with syntax error | This KPI represent a count of dump which occurred by syntax errors. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_DUMP | DEF_1DAY | 1 DA |
| EM_USED_P | Extended memory used | 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. This KPI is the amount of Extended Memory used. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 MI |
| ENQ_ARG_MAX_CNT | Max.num. of diff. lock arguments that the LT can contain | 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. This KPI is the maximal number of different lock arguments that can the Landscape Transformation (LT) possibly contain. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ARG_MAX_LVL | Max.num. of diff. lock arg. stored simultaneously in the LT | 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. This KPI is the maximal number of different lock arguments which are simultaneously stored in the Landscape Transformation (LT). | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ARG_NOW_LVL | Current 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. 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. This KPI counts the number of all different lock arguments stored in this lock table. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_BACKUP_REQ | Number of update calls for which locks were forwarded | This KPI counts number of update calls for which locks were forwarded. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_CLEAN_REQ | Number of releases of all locks of an 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. This KPI counts the number of all releases of all locks of a selected application server. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_COMPR_REQ | Compress Requests | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI | |
| ENQ_ENTR_MAX_CNT | Max.num. of elementary locks that the LT can contain | 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. This KPI is the maximal number of elementary locks that can the Landscape Transformation (LT) possibly contain. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ENTR_MAX_LVL | Max.num. of elementary locks stored simultaneously in the LT | 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. This KPI is the maximal number of elementary locks stored simultaneously in the Landscape Transformation (LT). | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ENTR_NOW_LVL | Current 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. This KPI is the current number of elementary locks stored in the lock table. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ENTR_P | Usage of SAP lock 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 (see Lock Collisions). If this is the case, the request is rejected. Otherwise, the new lock is written to the lock table. This KPI is percentage of lock table usage. | SAPSYS | SYS | application and database server | Central system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_ERROR_CNT | Number of errors that occurred during lock requests | This KPI is number of errors that occurred during lock requests. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_FILE_WRITE | Number of write accesses to file | This KPI is number of write accesses to file. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_FILE_WRT_BCK | Number of write accesses to backup file | This KPI is number of write accesses to backup file. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_OWN_MAX_CNT | Max.num. of lock owner IDs that can be stored in the LT | Lock owner is a person who holds a lock. A lock can have one or two owners. This KPI is the maximal number of lock owner IDs that can be possibly stored in the Landscape Transformation (LT). | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_OWN_MAX_LVL | Max.num. of lock owners stored simultaneously in the LT | Lock owner is a person who holds a lock. A lock can have one or two owners. This KPI is the maximal number of lock owners that are simultaneously stored in the Landscape Transformation (LT). | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_OWN_NOW_LVL | Current 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. To find out which user is currently holding a lock, use function module ENQUEUE_.... This KPI is the current number of all lock owners stored in the lock table. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_REPORT_REQ | Number of operations for reading the lock table | This KPI is number of operations for reading the lock table. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_REQ_REJ_CNT | Number of lock requests | This KPI is number of rejected lock requests. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_REQ_REJ_CNTD | Number of lock requests per minute since last run | This KPI is number of rejected lock requests per minute since last run. | SAPSYS | SYS | application and database server | Central system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_REQUEST_CNT | Number of rejected lock requests | Sm12 – statistics give the current value of ENQ processed. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_REQUEST_CNTD | Number of rejected lock requests per minute since last run | This KPI is 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 paralell processes. | SAPSYS | SYS | application and database server | Central system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_TOT_SER_TIME | Total time spent in the critical path of the LT for lock op. | 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. This KPI is the total time spent in the enqueue server. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_TOTAL_TIME | Total wait time of par. proc. before entering critical path | This KPI counts total time spent in the critical path of the Landscape Transformation for lock operations. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_TOTAL_WAIT | Total time spent in the enqueue server | This KPI counts total wait time of parallel processing before entering critical path. Waiting time for all work processes for accesing lock table. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_UPD_MAX_CNT | Max.num. of open update req. with locks occurred so far | This KPI is maximal number of accumulated update requests. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_UPD_NOW_LVL | Current number of open update requests with locks | This KPI is current number outstanding update requests. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| ENQ_VERIFY_REQ | Verify Requests | premenovat description na Verify Description a vyhodit z default | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_ENQUEUE_STAT | DEF_5MIN | 5 MI |
| FS_ROOT_FREE | Free space monitoring on root partiton | OS | SER | any server | Remote system | /DVD/MON_CL_COL_SYS_FS | |||
| GRC_AOC_BC_ALL | Number of SAP_BC roles having full auth. on org. level | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 DA | |
| GRC_AOC_SEC_ALL | Number of SAP_SEC_ roles having full auth. on org. level | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 DA | |
| GRC_AOC_ZCOM_ALL | Number of X,Y,Z* roles having full auth. on company code | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_AUTH_OC | GRC_1DAY | 1 DA | |
| GRC_PROF_PARAM | Num. of profile parameters with unexpected values | Collector checks values of profile parameters and compares it with values incollector’s input table. This procedure is performed for each server. KPI is the number of parameters which have different values from the values specified in input table. | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_PARAM | DEF_1DAY | 1 DA |
| HDB_BCK_DELAY_D | Time since 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).This KPI counts time since last successful DATA backup. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI |
| HDB_BCK_DELAY_L | 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. This KPI counts time since last succesful LOG backup. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI |
| HDB_BCK_FAILED | Number of failed backups | Media failure, human error and hardware failure are among the most common reasons backups fail. When the backup is performed with some errors, number of failed backups is recorded by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI |
| HDB_CPU_HOST | CPU utilizaton per host (avg 5 mins) | 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 CPU the most of the possible. Maximal CPU utilization per host displays avg utilization counted every 5 minutes. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_MAX_P | Max CPU utilizaton on all host (avg 5 mins) | 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 CPU the most of the possible. Maximal CPU utilization on all hosts is measured by this KPI. This KPI displays avg utilization counted every 5 minutes. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_SYS_P | CPU utilization by system (avg 5 mins) | 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. This KPI displays utilization of CPU by system counted every 5 minutes. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_SYS_SER | CPU utilization by system per host (avg 5 mins) | 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. CPU utilization by system per server is documented by KPI with name HDB_CPU_SYS_SER. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_USR_P | CPU utilization by users (avg 5 mins) | User utilization should not exceed a value of 50 to 60%. User CPU time is time spent on the processor running program's code (or code in libraries). This KPI displays situation, when CPU is utilized by user. In this situation avg utilization is counted every 5 minutes. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_USR_SER | CPU utilization by users per host (avg 5 mins) | User utilization should not exceed a value of 50 to 60%. User CPU time is time spent on the processor running your program's code (or code in libraries). When the CPU is utilized by users per server, this KPI counted utilization every 5 minutes. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_UTIL_P | Total CPU utilization (avg 5 mins) | 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%. When CPU utilization is maximum, this progress try to record this KPI. Value of utilization is measured in 5 minutes intervals. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_WIO_P | CPU utilization in I/O waits (avg 5 mins) | 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. This KPI show CPU utilization in I/O waits. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CPU_WIO_SER | CPU utilization in I/O waits per host (avg 5 mins) | 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. This KPI measures CPU utilization in I/O waits per server. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_CPU | HDB_5MIN | 5 MI |
| HDB_CS_DELRATIO | Delta memory / Total memory ratio | Percentage of delta memory versus total memory used. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_DELTASIZE | Size of column tables in delta memory | Total size of column table data in delta memory. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_ESTIMSIZE | Size of column tables estimated | Estimated size of column tables in memory. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_H_ESTSIZE | Size of column tables estimated per host | Estimated size of column tables in memory, per host. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_H_TOTSIZE | Total memory size of column tables per host | Total memory size of column tables per host. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_MAINSIZE | Size of column tables in 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. Size of column tables in main memory is captured by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_TOTALSIZE | Total memory size of column tables | Total memory size of column tables. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_UNLOADS | 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. The whole amount of unloads we can see in KPI with name HDB_CS_UNLOADS. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_UNLOADS04 | Number of unloads priority 0 to 4 | Number of unloads with priority 0 to 4 displays this KPI. These are 9 priorities. Priority 0 to 4 is the most important of these all priorities. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_UNLOADS56 | Number of unloads priority 5 to 6 | This KPI shows number of unloads priority 5 to 6. These are 9 priorities. Priority 5 to 6 is in the middle of these priorities. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_UNLOADS79 | Number of unloads priority 7 to 9 | KPI with name HDB_CS_UNLOADS79 measures number of unloads priority 7 to 9. These are 9 priorities. This priority is the least important. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_CS_UNLOADSL | Number of unloads due to low memory | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_TAB | 5 MI | ||
| HDB_DISK_D_TOTAL | Used space on data disk per host | Used space on data disk per host, absolute value in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_D_USED | Used space on data backup disk per host | Used space on data backup disk per host, absolute value in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_DATA | Total size of data disks | Used space on log backup disk per host, absolute value in GB | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_DBCK | Total used size on data disks | Used space on log disk per host, absolute value in GB | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_L_TOTAL | Used space on log backup disk per host | Used space on log backup disk per host, absolute value in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_L_USED | Used space on log disk per host | Used space on log disk per host, absolute value in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_LBCK | Total size of log disks | ? | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_LOG | Total used size on log disks | ? | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_MAXDATA | Max. used space on data disks | ? | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_MAXDBCK | Max. used space on data backup disks | Not displayed in charts | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_MAXLBCK | Max. used space on log backup disks | Not displayed in charts | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_MAXLOG | Max. used space on log disks | Total memory used by HANA database in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DISK_MAXUSED | Max. used disk space | 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DISK | HDB_5MIN | 5 MI |
| HDB_DM_COUNT | Number of small delta merge running for more than 60secs | This KPI monitors changes in .ini file contents. If there is a changed parameter since last monitoring run, it displays number of changes and related detail table shows list of changed parameters with OLD and NEW values | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DM | HDB_5MIN | 5 MI |
| HDB_DM_MAXRUN | Max. duration of small delta merge | Savepoints in HANA database are responsible for synchronization of memory pages with disks, which is necessary for system recovery. The frequency of savepoints is defined using parameter global.ini -> [persistence] -> savepoint_interval_s. If this KPI exceeds the interval significantly, it means savepoint was not successful and there is a synchronization issue. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DM | HDB_5MIN | 5 MI |
| HDB_DUMPS | Number of HANA dumps | 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_DUMP | HDB_5MIN | 5 MI |
| HDB_DUMPS_HOST | Number of HANA dumps per host | 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. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_DUMP | HDB_5MIN | 5 MI |
| HDB_FAILOVER | Number of hosts in failover status | 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 - FAQ: SAP HANA High Availability | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_IO_MINREAD | Min. 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. The KPI HDB_IO_MINREAD describe minimal value of I/O data read speed. | HANA | SYS | only application server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_MINWRITE | Min. 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. The KPI HDB_IO_MINWRITE describe minimal value of I/O data write speed. | HANA | SYS | only application server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_RR_DATA | Max. 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. This KPI shows max DATA read ratio. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_SER_READ | I/O data read speed per host | To achieve optimal database performance, I/O activity (read/write accesses) should be evenly distributed on the database's hard disks. DATA read ratio per server is displayed by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_SER_RR | 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. DATA read ratio per server is displayed by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_SER_WLOG | 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. This KPI measures LOG write ratio per server. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_SER_WR | 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. DATA write ratio per server is captured by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_SER_WRITE | 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. I/O data write speed server is collected by KPI with name HDB_IO_WR_DATA. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_WR_DATA | Max. DATA write 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. Maximal DATA write ratio is measured by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_IO_WR_LOG | Max. LOG write 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. This KPI shows maximal LOQ write ratio. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_IO | HDB_5MIN | 5 MI |
| HDB_BCK_FAIL_DAT | Number of failed DATA backups | When the DATA backup is performed with some errors, number of failed backups is recorded by this KPI. The KPI recognize two clasifications of failure on 'complete data backup' and 'data snapshot' | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 6 MI |
| HDB_BCK_FAIL_LOG | Number of failed LOG backups | When the LOG backup is performed with some errors, number of failed backups is recorded by this KPI. The KPI recognize two clasifications of failure on 'log backup' and 'log missing' | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 7 MI |
| HDB_LOG_BUFWAITP | Buffer switches with Wait on buffer semaphore % (max host) | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI | |
| HDB_LOG_BUFWAITT | Number of Buffer switches wait since last check | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI | |
| HDB_LOG_BUFWNOWT | Number of Buffer switches (noWait+wait) since last check | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI | |
| HDB_LOG_SEG_FREE | Minimum number of Free log segments (per hosts) | This KPI shows the lowest value for all the nodes (it does not show the value for each node).If this KPI is 0 then the log backup will be delayed and may cause crash. If low, see content of table /DVD/MON_HDBLOGS in the satellite system to see on which node is the issue. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI |
| HDB_LOG_SEG_TRNC | Maximum number of Truncated log segments (per hosts) | This KPI shows the highest value for all the nodes (it does not show the value for each node) If high value, see content of table /DVD/MON_HDBLOGS to see on which node is the issue. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_BCK | HDB_5MIN | 5 MI |
| HDB_MEM_ALLOCLIM | Global memory allocation limit for database | Not displayed in charts | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_CACHE_P | Memory used by caches per host | Percentage of host memory used by caches | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_CS_P | Memory used by column store per host | Percentage of host memory used by column store. If this component grows rapidly, consider housekeeping or archiving solutions. Check out DataVard OutBoard suite on www.datavard.com/outboard | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_HOST_P | Used 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. Percentage of utilization physical memory per host is displayed by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_MAX_P | Maximum used physical memory on 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. This KPI says about maximal using of physical memory on all hosts. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_SQL_P | Memory used by SQL exec & results per host | Percentage of host memory used by SQL execution and intermediate results. If this area grows, it can indicate too expensive/inefficient SQL statements. Please check list of expensive SQL statements in DB02 transaction. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_SRVHOSTP | Database memory used per host | Service used memory - an 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.This KPI displays the percentage of used service memory per host. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_SRVUSEDP | Maximum database memory used on hosts | This KPI calculates the % of max used memory on all hosts. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_STAT_P | Memory used by monitoring & statistics per host | 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 | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_SYS_P | Memory used by system per host | 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. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_TOTAL | Total physical memory on HANA available | Not displayed in charts | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_USED | Total physical memory used | 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. Total using of physical memory is represented by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_USED_DB | Total memory used by database | Total memory used by HANA database in GB | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MEM_USED_P | Total database memory used | 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MEM | HDB_5MIN | 5 MI |
| HDB_MVCC_CL_FILE | Number of cleanup file | Each undo or cleanup file in the system is represented by one row in this view. Undo files contain information needed for transaction rollback. These files are removed on transaction end. If data is deleted but must still be accessible because of MVCC isolation, the corresponding information is written to cleanup files. On transaction end cleanup files are passed to history management. Garbage collection uses the cleanup files to finally remove data. Undo files and cleanup files may be cached and reused because of performance issues. Cached files get assigned the type "FREE". Undo files for row store get the type "EXTERNALUNDO"With this KPI we can be alerted earlier when the GC is not working. Also If number is high, restart will be slow as it has to delete all temp files. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MVCC | HDB_5MIN | 5 MI |
| HDB_MVCC_MAXHOST | HDB MVCC max number of versions per host | 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. This KPI shows maximal number of versions per host using MVCC. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_MVCC | HDB_5MIN | 5 MI |
| HDB_NET_HOST_IN | HANA received via network - average per minute | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_INM | HANA received via network (max. minute avg. from all host) | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_IP | HANA received via network – traffic peak | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_IPM | HANA received via network – traffic peak from all hosts | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_OP | HANA sent via network – traffic peak | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_OPM | HANA sent via network – traffic peak from all hosts | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_OUM | HANA sent via network (max. minute avg. from all host) | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_HOST_OUT | HANA sent via network - average per minute | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | 5 MI | ||
| HDB_NET_PING | HANA Network Client Duration - per host | The measured ping times include the communication between nameserver and indexserver and KPI collection within the indexserver. Increased times can be a symptom of an underlying performance issue. Check for general issues impacting the performance (e.g. resource bottlenecks). | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NET_RATIO | HANA Network Client Duration - max all hosts | 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 | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NET_SPEED | HANA Network Server Duration - per host | 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 | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NET_TRAFFIC | HANA Network Server Duration - max all hosts | 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 | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETCLI | HANA Network Service response time - per host | HANA Network Client Duration per host is displayed by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETCLIM | HANA Network Service response time - max all hosts | This KPI shows HANA Network Client Duration - max all hosts. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETSER | Index server ping time per host | Server duration per host is measured by KPI with name HDB_NETSER. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETSERM | Network I/O ratio | HANA Network Server Duration - max all hosts is displayed by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETSERVRESP | Network throughput | Service response time per host for HANA Network is captured by this KPI. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_NETSERVRESPM | Network traffic in last 5 minutes | This KPI shows HANA Network Service response time - max all hosts. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_NET | HDB_5MIN | 5 MI |
| HDB_OLCK_AGE | Age of the oldest Object Lock | 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, many threads…). Monitoring view M_OBJECT_LOCKS provides the status of currently acquired locks on objects with detailed information such as lock acquisition time, lock mode. The KPI HDB_OLCK_AGE "Age of the oldest Object Lock" is the oldest lock as shown by monitoring view M_OBJECT_LOCKS. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_OBJECTLOCK | HDB_5MIN | 5 MI |
| HDB_OLCK_COUNTX | Number of Object Locks older than 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, many threads…). Monitoring view M_OBJECT_LOCKS provides the status of currently acquired locks on objects with detailed information such as lock acquisition time, lock mode. The KPI HDB_OLCK_COUNTX "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. X is customizable with collector parameter LOCK_COUNT_OLDER_X_MINUTES, by default 5 minutes. Number of object lock older than X minutes is displayed by KPI with name HDB_OLCK_COUNTX. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_OBJECTLOCK | HDB_5MIN | 5 MI |
| HDB_PARAM_CH | Count of changed HANA parameters | This KPI monitors changes in .ini file contents. If there is a changed parameter since last monitoring run, it displays number of changes and related detail table shows list of changed parameters with OLD and NEW values | HANA | SYS | only application server | Remote system | /DVD/MON_HDB_CL_COL_PAR | HDB_5MIN | 5 MI |
| HDB_PART_CNT_ABX | Number or partitions above XXX million rows | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_1DAY | 1 DA | |
| HDB_PCACHE_HR_SR | SQL Plan Cache Hit Ratio per host | The hit ratio is the percentage of pages found in the cache without having to read from the disk. The ratio shows the average percentage of data pages found in the cache since SQL Server was started. This KPI displays SQL Plan Cache Hit Ratio per host. | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 MI |
| HDB_PLANCACHE_HR | Min. SQL Plan Cache Hit Ratio | The hit ratio is the percentage of pages found in the cache without having to read from the disk. The ratio shows the average percentage of data pages found in the cache since SQL Server was started. Minimal SQL Plan Cache Hit Ratio is measured by this KPI. | HANA | SYS | only application server | Remote system | /DVD/MON_HDB_CL_COL_SQL_PLAN | HDB_5MIN | 5 MI |
| HDB_REP_DELAY | System replication: Log shipping delay | 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 | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_REP_ERROR | Number of system replication errors | There was an error 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 | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_REP_SS_AGE | Age of 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 | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_REP_UNKNOWN | Number of unknown replication statuses | There was an error 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 | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_RS_ALLOC | Row store allocated size | This KPI shows row store allocated size. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_RS_FRAG | Row store fragmentation | 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TAB | HDB_5MIN | 5 MI |
| HDB_SP_COUNT | Number of savepoints | During a savepoint, the database system writes the data which has changed since the last savepoint from the data cache (working memory) to the data area (permanent storage). The data written during a savepoint always represents a consistent state of the database. During a savepoint the database system does not overwrite the pages written to the data area at the previous savepoint, but instead writes the changed data to free positions. This is because the database system requires this information from the previous savepoint for a restart if there is a system failure during the new savepoint. Only after the database system has successfully completed the new savepoint does it release the pages of the old savepoint in the data area for overwriting. This KPI shows number of savepoints. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 MI |
| HDB_SP_LAST | Time since last savepoint | Savepoints in HANA database are responsible for synchronization of memory pages with disks, which is necessary for system recovery. The frequency of savepoints is defined using parameter global.ini -> [persistence] -> savepoint_interval_s. If this KPI exceeds the interval significantly, it means savepoint was not successful and there is a synchronization issue. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 MI |
| HDB_SP_MAXRUN | Max. duration of a savepoint | During a savepoint, the database system writes the data which has changed since the last savepoint from the data cache (working memory) to the data area (permanent storage). The data written during a savepoint always represents a consistent state of the database. During a savepoint the database system does not overwrite the pages written to the data area at the previous savepoint, but instead writes the changed data to free positions. This is because the database system requires this information from the previous savepoint for a restart if there is a system failure during the new savepoint. Only after the database system has successfully completed the new savepoint does itrelease the pages of the old savepoint in the data area for overwriting. This KPI shows maximal duration of savepoint. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 MI |
| HDB_SP_MAXRUN_C | Max. critical phase duration of a savepoint | During a savepoint, the database system writes the data which has changed since the last savepoint from the data cache (working memory) to the data area (permanent storage). The data written during a savepoint always represents a consistent state of the database. During a savepoint the database system does not overwrite the pages written to the data area at the previous savepoint, but instead writes the changed data to free positions. This is because the database system requires this information from the previous savepoint for a restart if there is a system failure during the new savepoint. Only after the database system has successfully completed the new savepoint does it release the pages of the old savepoint in the data area for overwriting. To perform a savepoint write operation, SAP HANA needs to take a global database lock. This period is called the “critical phase” of a savepoint. The max. critical phase duration of a savepoint is displayed by this KPI. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 MI |
| HDB_SP_SPEED | Savepoint speed | During a savepoint, the database system writes the data which has changed since the last savepoint from the data cache (working memory) to the data area (permanent storage). The data written during a savepoint always represents a consistent state of the database. During a savepoint the database system does not overwrite the pages written to the data area at the previous savepoint, but instead writes the changed data to free positions. This is because the database system requires this information from the previous savepoint for a restart if there is a system failure during the new savepoint. Only after the database system has successfully completed the new savepoint does it release the pages of the old savepoint in the data area for overwriting. This KPI shows savepoint speed. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_SP | HDB_5MIN | 5 MI |
| HDB_SRV_RESTART | Number of restarted index services | Restart of an index server can indicate a node failover or another crash situation. | HDB_HA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_HA | HDB_5MIN | 5 MI |
| HDB_THR_BACKUP | Max. 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. Maximum duration of backup threads are displayed by KPI is called HDB_THR_BACKUP. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_COUNT | Number of active HANA threads | 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. The active threads, which exists in HANA are monitored by KPI with name HDB_THR_COUNT. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_JOBWRUN | Thread JobWorker Running max all hosts | HANA | SYS | any server | Central system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_JOBWRUNH | Thread JobWorker Running per host | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_JOBWTTL | Thread JobWorker Total max all hosts | HANA | SYS | any server | Central system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_JOBWTTLH | Thread JobWorker Total per host | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_LOCKED | Number of threads waiting for locks | Number of threads waiting for various types of locks. If there are long running locks, please find the lock type in the detail table with threads and check SAP Note 1999998 - FAQ: SAP HANA Lock Analysis | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_MAXRUN | Max. duration of HANA threads | Maximum duration of all running HANA threads. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_MERGEDOG | Max. 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. This KPI shows maximal duration of MergeDog threads. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_REPLICA | Maximum runtime of replications | This is the time taken for replicating the data from primary site to secondary. Long time of replication is always after the back up. So, it can be co-related with the KPI Max duration of backup thread. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_SQLEC1 | Thread SqlExecutor Count Running > 1minute | HANA | SYS | any server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_SQLERUN | Thread SqlExecutor Running max all hosts | HANA | SYS | any server | Central sustem | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_SQLERUNH | Thread SqlExecutor Running per host | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_SQLETTL | Thread SqlExecutor Total max all hosts | HANA | SYS | any server | Central system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_SQLETTLH | Thread SqlExecutor Total per host | HANA | SER | only database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI | |
| HDB_THR_SQLRUN | Max. 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. This KPI shows maximal duration of SqlExecutor threads. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_THR_TIME_CAP | Time to capture threads | Runtime to read all thread data from HANA monitoring view | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_THREAD | HDB_5MIN | 5 MI |
| HDB_TRAN_BLOCK_C | 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. This KPI shows number of blocked transactions. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 MI |
| HDB_TRAN_BLOCK_T | Duration of longest transaction lock wait | 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 MI |
| HDB_TRAN_REDO | Maximum redo size of current transaction | To enable point-in-time recovery for the database system, the DB writer REDO logs after every COMMIT. These logs are used to reply changes recorded since last full backup. Check if you can reduce the amount of performed change operations. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 MI |
| HDB_TRAN_UNDO | Maximum undo size of current transaction | 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 commited 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. | HANA | SYS | application and database server | Remote system | /DVD/MON_HDB_CL_COL_TRAN | HDB_5MIN | 5 MI |
| HMBS_A_HK | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMBS_A_HK | ||
| HMBS_A_TTB | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMBS_A_TTB | ||
| HMBS_E_HK | HeatMap: ETL Profile - Dummy KPI | HMCCAE | SYS | any server | Central system | /DVD/HMCC_CL_COL_RL_ETL | HMBS_E_HK | ||
| HMBS_E_RAL | HeatMap: ETL Profile - Dummy KPI | HMCCAE | SYS | any server | Central system | /DVD/HMCC_CL_COL_RL_ETL | HMBS_E_RAL | ||
| HMBS_E_SS | HeatMap: ETL Profile - Dummy KPI | HMCCAE | SYS | any server | Central system | /DVD/HMCC_CL_COL_RL_ETL | HMBS_E_SS | ||
| HMBS_S_STD | HeatMap: ETL Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMBS_COL_STAD | HMBS_S_STD | 10 MI | |
| HMBW_DU_RECORD | HMBW Data Usage collected records | HMBW | SYS | any server | Central system | /DVD/MON_HM_CL_COL_DU | HMBW_1DAY | ||
| HMBW_DU_RECORD_R | HMBW Data Usage collected - remote | HMBW | SYS | any server | Remote system | /DVD/MON_HM_CL_COL_DU | HMBW_1DAY | ||
| HMBW_QU_RECORD | HMBW QueryUsage collected records | HMBW | SYS | any server | Central system | /DVD/MON_HM_CL_COL_QU | HMBW_1DAY | 1 DA | |
| HMBW_QU_RECORD_R | HMBW Query Usage collected - remote | HMBW | SYS | any server | Remote system | /DVD/MON_HM_CL_COL_QU | HMBW_1DAY | 1 DA | |
| HMCC_A | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | |||
| HMCC_E | HeatMap: ETL Profile - Dummy KPI | HMCCAE | SYS | any server | Central system | /DVD/HMCC_CL_COL_RL_ETL | |||
| HMER_A_ACH | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_ACH | ||
| HMER_A_ACO | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_ACO | ||
| HMER_A_AEC | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_AEC | ||
| HMER_A_AFI | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_AFI | ||
| HMER_A_ALE | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_ALE | ||
| HMER_A_AMM | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_AMM | ||
| HMER_A_ASD | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_ASD | ||
| HMER_A_UEG | HeatMap: Analysis Profile - Dummy KPI | HMCCAE | SYS | any server | Remote system | /DVD/HMCC_CL_COL_RL_ANL | HMER_A_UEG | ||
| HMER_C_CCL | HeatMap: Central Collector - Dummy KPI | HMCCAE | SYS | any server | Central system | /DVD/EHMC_CL_COL_CCLDR | HMER_C_CCL | ||
| IDOC_I_PROC_AVG | Total count of inbound IDocs for last snapshot | IDOC | SYS | only application server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO | |
| IDOC_IN_ERRORS | Number of Errors in Inbound iDocs Processing | List of iDoc Inbound statuses which indicates error and are counted to 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 | IDOC | SYS | application and database server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO |
| IDOC_INBOUND_C | Average time of successfull inbound IDoc processing (50-53) | IDOC | SYS | only application server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO | |
| IDOC_O_PROC_AVG | Total count of outbound IDocs for last snapshot | IDOC | SYS | only application server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO | |
| IDOC_O_TRANS_AVG | Nummber of Errors in Outbound iDocs processing | IDOC | SYS | only application server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO | |
| IDOC_OUT_ERRORS | Average time of successfull outbound IDoc processing (01-30) | List of Outbound iDoc statuses which indicate error and are counted to 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 | IDOC | SYS | application and database server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO |
| IDOC_OUTBOUND_C | Average time of successful transmission (03->12) | IDOC | SYS | only application server | Remote system | /DVD/MON_IDOC_CL_COL_EDIDC | IDOC_1HOUR | 1 HO | |
| LAN_ERROR_IN | Network errors In | This KPI counts the number of network errors In. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| LAN_ERROR_OUT | Network errors Out | This KPI counts the number of network errors Out. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| LAN_PACKETS_IN | Network packets In | This KPI counts the number of network packets In. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| LAN_PACKETS_OUT | Network packets Out | This KPI counts the number of network packets Out. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| MEM_FREE | Memory free (server) | This KPI is free memory on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| MEM_FREE_SUM | Total free memory in system (all servers) | This KPI is total free memory in system on all servers. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| MEM_PHYS | Physical memory available (server) | This KPI is available physical memory on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 DA |
| MEM_USED_P | Memory used (server) | This KPI is used memory on the server. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| PAGE_IN | Kb paged in/s | Page IN from memory per hour. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| PAGE_IN_P | Page IN from memory per hour | The memory utilization statistics are important to ensure that system performance is running smoothly. This KPI displays the number of pages in per hour. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| PAGE_OUT | Kb paged out/s | 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.Valuesare 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. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| PAGE_OUT_P | Page OUT from memory per hour | The memory utilization statistics are important to ensure that system performance is running smoothly. This KPI displays the number of pages out per hour. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| PARAM_CHANGED | Number of changed system profile parameters | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_PARAM | DEF_1DAY | 1 DA | |
| RFC_CIF_IN_15 | tRFCqIN number of entries Queue CIF older than 15minutes | 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. This KPI shows tRFCqIN number of entries Queue CIF older than 15 minutes. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_RFCQ | DEF_1HOUR | 1 HO |
| RFC_CIF_OUT_15 | tRFCqOUT number of entries Queue CIF older than 15minutes | 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. This KPI shows tRFCqOUT number of entries Queue CIF older than 15 minutes. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_RFCQ | DEF_1HOUR | 1 HO |
| RFC_IN_AUTHERR | Number of failed RFC tests - RFC check with authorisation | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_RFC | 1 HO | ||
| RFC_IN_CON_ERR | Number of failed RFC tests - RFC check without authorisation | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_RFC | 1 HO | ||
| RFC_IN_PINGERR | Number of failed RFC tests - ping server IP | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_RFC | 1 HO | ||
| ROLL_USED_P | 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. This KPI is the amount of Roll area used. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_BUFF | DEF_5MIN | 5 MI |
| SERVER_IS_DOWN | Server is down (true = 1 / false = 0 ) | 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 server is running. . This KPI has no collector assign as it is hardcoded in CanaryCode. | OS | SER | application and database server | Central system | DEF_1MIN | 1 MI | |
| SERVER_RFC_FAIL | Server unreachable via RFC (true = 1 / false = 0) | KPI similar to SERVER_IS_DOWN KPI but is more sensitive. Value 1 that means server cannot be reached 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 assign as it is hardcoded in CanaryCode | SAPSYS | SER | application and database server | Central system | DEF_1MIN | 1 MI | |
| SLG_DEBUG | Number of changes in debug mode | GRC | SYS | application and database server | Remote system | /DVD/MON_GRC_CL_COL_SYSLOG | DEF_1HOUR | 1 HO | |
| SLG_KERNEL | Number of activated C-calls debuging | GRC | SYS | application and database server | Remote system | /DVD/MON_GRC_CL_COL_SYSLOG | DEF_1HOUR | 1 HO | |
| STAT_DIALOG_AVG | Average System Response Time for Users | 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. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_DIALOG_TOT | 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. Total system response time for users is measured by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_M_RESP_BC | [BC] 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. Response time from Basis Components is measured by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_M_RESP_BW | [BW] 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. This KPI shows response time from SAP Business Inf. Warehouse. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_M_RESP_XXXX | Total response time from undefined components | 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.This KPI shows total response time from components, which are undefined. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_M_TCNT_BC | [BC] Number of trans. 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. Number of trans. from Basis Components is processed by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_M_TCNT_BW | [BW] Number of trans. 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. Number of trans. from SAP Business Inf. Warehouse is proceseed by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_M_TCNT_XXXX | Number of transaction from undefined components | Number of transaction from undefined components is displayed by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_1HOUR | 1 HO |
| STAT_RSA1_AVG | Average runtime of RSA1 | RSA1 - Modeling - DW Workbench. Average runtime of RSA1 is displayed by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_SE16_AVG | Average Response Time of Transaction SE16 | SE16 - Data Browser. Average response time of transaction is processed by KPI with name STAT_SE16_AVG. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_SE16_CNT | Number of SE16 Transaction starts | SE16 - Data Browser. Number of SE16 Transaction starts is displayed by this KPI. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_SE16_TTL | Response Time of Transaction SE16 | SE16 - Data Browser. This KPI shows response time of transaction SE16. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_SE38_RESP | Response Time of Transaction SE38 | SE38 -ABAP Editor. This KPI shows response time of transaction SE38. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| STAT_SE38_RUN | Average Runtime of reports running via SE38 | SE38 -ABAP Editor. Average Runtime of reports running via transaction SE38. | STAT | SYS | application and database server | Remote system | /DVD/MON_STAT_CL_COL_MODULES | STAT_5MIN | 5 MI |
| SWAP_CONF | Swap configured | This KPI is amount of configured swap space. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1DAY | 1 DA |
| SWAP_DELTA | Delta between previous and current used swap | 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. | OS | SER | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| SWAP_DELTA_P | Delta between previous and current used swap | 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’s 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. | OS | SER | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| SWAP_DELTA_PMAX | Delta between swap (max all servers) | 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. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_1MIN | 1 MI |
| SWAP_FREE | Free swap space | Free Swap in percentage of total swap. When it reach 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. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| SWAP_USED | Used swap space | This KPI is amount of used swap space - in kB. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| SWAP_USED_P | Used swap space | KPI calculates percentages of used swap space by substituting actual value SWAP_FREE from SWAP_CONF. | OS | SER | only application server | Remote system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| SWAP_USED_PMAX | Used swap (max all servers) | 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. | OS | SYS | only application server | Central system | /DVD/MON_CL_COL_MEM_CPU_LAN | DEF_5MIN | 5 MI |
| SYSTEM_IS_DOWN | System is down (true = 1 / false = 0 ) | Special KPI hardcoded in Canarycode ie without collector, value 1 if SID is not responding (rfc call not possible to satellite system). Can be used for alerting. | SAPSYS | SYS | application and database server | Central system | DEF_1MIN | 1 MI | |
| UPD_REQ_CANCEL | Update requests cancelled | 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 canceleled, this situation is displayed by this KPI. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_UPD_REQ | DEF_1HOUR | 1 HO |
| UPD_REQ_TOBEUPD | Update requests to be updated | 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. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_UPD_REQ | DEF_1HOUR | 1 HO |
| USER_CNT | Number of active users | This KPI is number of active users. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI |
| USER_CNT_SER | Number of active users (server) | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI | |
| USER_EXT_MOD | Number of external modes | This KPI is number of external modes. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI |
| USER_EXT_MOD_SER | Number of external modes(server) | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | |||
| USER_GUI_CNT | Number of interactive users | This KPI is number of interactive users. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI |
| USER_GUI_CNT_SER | Number of interactive users(server) | /DVD/MON_CL_COL_USER_INFO | |||||||
| USER_INT_MOD | Number of internal modes | This KPI is number of active users. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI |
| USER_INT_MOD_SER | Number of internal modes(server) | /DVD/MON_CL_COL_USER_INFO | |||||||
| USER_RFC_CNT | Number of RFC-users | This KPI is number of RFC-users. | SAPSYS | SYS | application and database server | Remote system | /DVD/MON_CL_COL_USER_INFO | DEF_5MIN | 5 MI |
| USER_RFC_CNT_SER | Number of RFC-users(server) | /DVD/MON_CL_COL_USER_INFO | |||||||
| WP_BTC_CONF | Number of BTC configured (server) | 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 %. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 HO |
| WP_BTC_CONF_SUM | Number of BTC configured (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 HO |
| WP_BTC_USED | Number of used BTC (server) | This KPI counts number of used BTC work processes on the server. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_BTC_USED_MAX | Usage of BTC (max all servers) | KPI value determines number of BTC work processes (WP) of server with the highest amount of BTC WP - returns value of the busiest server. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_BTC_USED_P | Usage of BTC (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_BTC_USED_S_P | Number of used BTC (all servers) | For the WP info we calculate the number of batch workprocesses (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. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_BTC_USED_SUM | Usage of BTC (all servers) | Count the number of used DIA workprocesses captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for all application servers. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_COMMIT | Number of WP in COMMIT state | This kpi counts the number of WP in COMMIT state captured in sm66 (saved in /DVD/MON_WPINFO on the central instance). | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_CONF | Number of DIA configured (server) | This KPI is the number of DIA work processes configured on the server. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 HO |
| WP_DIA_CONF_SUM | Number of DIA configured (all servers) | This KPI is the number of DIA work processes configured on all servers. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1HOUR | 1 HO |
| WP_DIA_LONGR | Longest running DIA WP (server) | This KPI is longest running DIA work process - in seconds. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_LONGR_MAX | Longest running DIA WP (max all servers) | Max value of runtime of DIA WP captured in sm66 (saved in /DVD/MON_WPINFO on the central instance). | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_NBR_AT | Number of long running DIA WP (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_NBR_ATDU | Number of long running DIA WP for Dialog User (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_NBR_ATDUS | Number of long running DIA WP for Dialog User (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_NBR_ATSUM | Number of long running DIA WP (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_DIA_RT_AVG | Avg. runtime of DIA processes (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_RT_AVG_A | Avg. runtime of DIA processes (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_USED | Number of used DIA (server) | This KPI counts number of used dialog WP on server. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_USED_MAX | Number of used DIA (max all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_USED_P | Usage of DIA (server) | 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 behaviour, unless CPU load goes above 80%. Some charts display Used DIA% = 100% - Free DIA %. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_USED_S_P | Number of used DIA (all servers) | Number of free DIA WP (for the instance) divided by total number of DIA WP. Workprocess Info (ie SM66) is captured every 5 minutes. For the WP info we calculate the number of dialog workprocesses(DIA WP) currently used for the system (SID), in percentage of total number of DIA WP configured in this system. ie it's not looking at specific application server but calculated for the sum of all application server. 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 behaviour, unless CPU load goes above 80%. Some charts display Used DIA % = 100 % - Free DIA %. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_DIA_USED_SUM | Usage of DIA (all servers) | Count the number of used DIA workprocesses captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for all application servers. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_MAX_REPORT | Number of WP on same report (all servers) | Count the number of workprocesses (DIA or BTC) on the same report captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for all users. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_MAX_TABLE | Number of WP on same table (all servers) | Count the number of workprocesses (DIA or BTC) on the same table name, captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for all users. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_MAX_USER | Number of WP with the same user (all servers) | Count the number of workprocesses (DIA or BTC) with the same user captured in sm66 (saved in /DVD/MON_WPINFO on the central instance), for user type ‘A’:Dialog user. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_NRIV | Number of WP accessing number ranges | Count number of WP captured in sm66 (saved in /DVD/MON_WPINFO on the central instance) showing table = NRIV. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1MIN | 1 MI |
| WP_SAPLSENA | Number of WP calling ENQUEUE | This kpi counts 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. | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_UP2_CONF | Number of UP2 configured (server) | This KPI is number of configured work processes for task processing on server - these tasks are in update process with the priority V2. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 DA |
| WP_UP2_CONF_SUM | Number of UP2 configured (all servers) | This KPI is number of configured work processes for task processing on all servers - these tasks are in update process with the priority V2. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 DA |
| WP_UP2_USED | Number of used UP2 (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_UP2_USED_SUM | Number of used UP2 (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_UPD_CONF | Number of UPD configured (server) | This KPI is number of configured work processes for task processing on server - these tasks are in update process with the highest priority (V1). | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 DA |
| WP_UPD_CONF_SUM | Number of UPD configured (all servers) | 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). | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_1DAY | 1 DA |
| WP_UPD_USED | Number of used UPD (server) | 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. | SAPSYS | SER | only application server | Remote system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| WP_UPD_USED_SUM | Number of used UPD (all servers) | 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. | SAPSYS | SYS | only application server | Central system | /DVD/MON_CL_COL_GET_WP | DEF_5MIN | 5 MI |
| SDTR_ERROR_CNT | Number of all transmission in error | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 HO | |
| SDTR_TRANSMT_CNT | Number of successfully transmitted mail requests | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 HO | |
| SDTR_WAITING_CNT | Number of waiting transmissions | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_SEND_TRANSMIT | DEF_1HOUR | 1 HO | |
| USR_STAT_INACT6M | Number of inactive user not logon in last 6 months | SAPSYS | SYS | only application server | Remote system | /DVD/MON_CL_COL_USR_STAT | DEF_1DAY | 1 DA | |
| GRC_REF_USR_CNT | Number of used reference users | GRC | SYS | any server | Remote system | /DVD/MON_GRC_CL_COL_REF_USERS | 1 MI | ||
| GRC_SEC_NOTE_CNT | Number of not implemented security notes | SAPSYS | SYS | any server | Remote system | /DVD/MON_GRC_CL_COL_SEC_NOTES | |||
| GRC_AUTH_ALL | Number of user with full authorization (SAP_ALL,SAP_NEW) | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_USR_AUTH | GRC_1DAY | 1 DA | |
| GRC_AUTH_ALL_O_N | Number of NEW users with full authorization(SAP_ALL,SAP_NEW) | GRC | SYS | only application server | Remote system | /DVD/MON_GRC_CL_COL_USR_AUTH | |||
| ORA_LOG_00060 | ORA-00060 - Deadlock detected while waiting for resource | ORACLE | SYS | any server | Remote system | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 MI | |
| ORA_LOG_01578 | ORA-01578 - Data block corrupted | ORACLE | SYS | any server | Remote system | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 MI | |
| ORA_LOG_01653 | ORA-01653 - Unable to extend table *.* by * in tablespace * | ORACLE | SYS | any server | Remote system | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 MI | |
| ORA_LOG_27072 | ORA-27072 - File I/O error | ORACLE | SYS | any server | Remote system | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 MI | |
| ORA_LOG_30036 | ORA-30036 - Unable to extend segm. by * in undo tab.sp. '*' | ORACLE | SYS | any server | Remote system | /DVD/MON_ORA_CL_COL_ALERTLOG | ORA_5MIN | 5 MI | |
| OS_RUN_PS_COUNT | Get number of running processes on OS | OS | SYS | only application server | Remote system | /DVD/MON_CL_COL_SYS_CMD | |||
| VFORGE_SP_U | SystemProfiler: Number of Undefined findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_BITC | VF | ||
| VFORGE_SP_X_3 | SystemProfiler: Number of low impact errors | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_BITC | VF | ||
| VFORGE_SP_X_5 | SystemProfiler: Number of medum impact errors | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_BITC | VF | ||
| VFORGE_SP_X_7 | SystemProfiler: Number of high impact errors | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_BITC | VF | ||
| VFORGE_SP_X_9 | SystemProfiler: Number of very high impact errors | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_BITC | VF | ||
| VFORGE_CP_AUTH | Missing AUTHORITY-CHECK in Reports | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VFORGE_CP_DB_MOD | Direct Database Modification | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VFORGE_CP_INJECT | ABAP Command injection | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VFORGE_CP_OS_INJ | OS Command Injection | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_COMP | CodeProfiler: Compliance findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_DLP | CodeProfiler: Data-Loss Prevention findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_MNT | CodeProfiler: Maintainability findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_PERF | CodeProfiler: Performance findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_ROB | CodeProfiler: Robustness findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| VF_TD_SECUR | CodeProfiler: Security findings | VFORGE | SYS | only application server | Remote system | /DVD/MON_VF_CL_COL_CP | VF | ||
| KTEWR_ASIA | Web report response times in Asia | SYS | only application server | Remote system | |||||
| KTEWR_EUROPE | Web report response times in Europe | SYS | only application server | Remote system | |||||
| KTEWR_USA | Web report response times in USA | SYS | only application server | Remote system |