This topic describes key metrics of OceanBase Database, clusters, tenants, and hosts.
Query monitoring items
You can query the definitions of all monitoring items in the sys tenant by using SQL statements. Here is an example:
obclient> SELECT STAT_ID, CLASS, NAME FROM V$STATNAME;
Many monitoring items are associated with internal implementations. Therefore, they may be changed or deleted. For details about how to query monitoring items of a specific category, see Monitor items.
Monitoring item categories
OceanBase Database V4.x supports 15 categories and more than 600 monitoring items, covering all critical execution information such as network, request queues, transactions, SQL, cache, storage, resource quotas, and logs. The specific categories are as follows:
| Monitoring item category ID | Category | Description |
|---|---|---|
| 1 | NETWORK | Network |
| 2 | QUEUE | Request queue |
| 4 | TRANS | Transaction |
| 8 | SQL | SQL |
| 16 | CACHE | Cache |
| 32 | STORAGE | Storage |
| 64 | RESOURCE | Resource |
| 128 | DEBUG | Log |
| 256 | CLOG | CLOG |
| 512 | ELECT | Election |
| 1024 | OBSERVER | System |
| 2048 | RS | Root Service |
| 3072 | Time Model | Time model |
| 4096 | TABLEAPI | TableAPI |
| 8192 | WR | WR |
Network
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 10000 | 1 | rpc packet in | The total number of RPC packets received by the tenant. The count increases by 1 when the tenant receives an RPC request or receives a response after sending an RPC request. |
| 10001 | 1 | rpc packet in bytes | The total number of bytes of RPC packets received by the tenant, in bytes. The count increases by the size of the RPC request or response when the tenant receives an RPC request or receives a response after sending an RPC request. |
| 10002 | 1 | rpc packet out | The total number of RPC packets sent by the tenant. The count increases by 1 when the tenant sends an RPC request or sends a response after receiving an RPC request. |
| 10003 | 1 | rpc packet out bytes | The total number of bytes of RPC packets sent by the tenant, in bytes. The count increases by the size of the RPC request or response when the tenant sends an RPC request or sends a response after receiving an RPC request. |
| 10004 | 1 | rpc deliver fail | The total number of failures when an RPC request is forwarded to the tenant's work queue. The count increases by 1 when the RPC IO thread fails to forward an RPC request to the tenant's work queue. |
| 10005 | 1 | rpc net delay | The total network transmission delay of RPC requests received by the tenant, in microseconds. After an RPC IO thread parses an RPC request, it calculates the difference between the current timestamp and the timestamp obtained from the packet header and accumulates this value to the RPC_NET_DELAY metric. |
| 10006 | 1 | rpc net frame delay | The total network frame processing time of RPC requests received by the tenant, in microseconds. After an RPC IO thread forwards an RPC request to the tenant's work queue, it calculates the difference between the current timestamp and the timestamp recorded when the RPC packet was parsed and accumulates this value to the RPC_NET_FRAME_DELAY metric. |
| 10007 | 1 | mysql packet in | The total number of SQL request packets received by the tenant. This value increases by 1 after a network thread decodes a complete SQL request packet. |
| 10008 | 1 | mysql packet in bytes | The total number of bytes of SQL request packets received by the tenant, in bytes. This value is obtained based on the size of the original data packets received by the network thread, according to the protocol rules. |
| 10009 | 1 | mysql packet out | The total number of SQL response packets sent by the tenant. This value increases by 1 after a network thread encodes and sends a complete response packet. |
| 10010 | 1 | mysql packet out bytes | The total number of bytes of SQL response packets sent by the tenant, in bytes. This value is obtained based on the size of the encoded response results. |
| 10011 | 1 | mysql deliver fail | The total number of failures when SQL login requests are added to the login queue and other requests are added to the work thread queue. For login requests, this value increases by 1 when the login request thread queue is full. For other requests, this value increases by 1 when the tenant's work thread queue is full. |
| 10012 | 1 | rpc compress original packet cnt | The total number of RPC requests that specify the need for compression. This value increases by 1 when an RPC request is sent and the compressor_type is set. |
| 10013 | 1 | rpc compress compressed packet cnt | The total number of compressed RPC requests sent by the tenant. This value increases by 1 when an RPC request is sent, the compressor_type is set, and the compression is successful (the compressed size is smaller than the original size). |
| 10014 | 1 | rpc compress original size | The total original size of RPC requests that specify the need for compression, in bytes. This value is accumulated to the RPC_COMPRESS_ORIGINAL_SIZE metric when an RPC request is sent and the compressor_type is set. |
| 10015 | 1 | rpc compress compressed size | The total compressed size of compressed RPC requests sent by the tenant, in bytes. This value is accumulated to the RPC_COMPRESS_COMPRESSED_SIZE metric when an RPC request is sent, the compressor_type is set, and the compression is successful. |
| 10016 | 1 | rpc stream compress original packet cnt | This metric is deprecated in V4.x and is retained only in the code, in times. |
| 10017 | 1 | rpc stream compress compressed packet cnt | This metric is deprecated in V4.x and is retained only in the code, in times. |
| 10018 | 1 | rpc stream compress original size | This metric is deprecated in V4.x and is retained only in the code, in bytes. |
| 10019 | 1 | rpc stream compress compressed size | This metric is deprecated in V4.x and is retained only in the code, in bytes. |
| 110000 | 1 | standby fetch log bytes | The total number of bytes received by the OBServer node during network-based standby log synchronization. This value is recorded in the STANDBY_FETCH_LOG_BYTES metric. |
| 110001 | 1 | standby fetch log bandwidth limit | The allocated bandwidth for network-based standby log synchronization. This value is recorded in the STANDBY_FETCH_LOG_BANDWIDTH_LIMIT metric. |
Request queue
| Metric ID | Metric type | Metric name | Description |
|---|---|---|---|
| 20000 | 2 | request enqueue count | The total number of requests enqueued for the tenant. Each time a request is enqueued into the worker thread queue, the count increases by 1. |
| 20001 | 2 | request dequeue count | The total number of requests dequeued for the tenant. Each time a request is dequeued from the worker thread queue, the count increases by 1. |
| 20002 | 2 | request queue time | The total time that all requests of the tenant wait in the queue, in microseconds. When a worker thread of the tenant acquires a request, the time between the current time and the time when the request was enqueued into the queue is calculated and added to the REQUEST_QUEUE_TIME metric. |
Transactions
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 30000 | 4 | trans commit log sync time | The cumulative time spent by the tenant on this server for a transaction to successfully commit to a majority of replicas, measured in microseconds. When a transaction successfully commits to a majority of replicas, the current time is subtracted from the time when the commit was successful, and the time spent on the majority is added to this metric. |
| 30001 | 4 | trans commit log sync count | The number of times the tenant has successfully committed and completed a majority of replicas on this server. Each time a transaction successfully commits to a majority of replicas, the count is incremented. |
| 30002 | 4 | trans commit log submit count | The number of times the tenant has submitted a commit log on this server. Each time a commit log is successfully submitted (without guaranteeing a majority), the count is incremented. |
| 30005 | 4 | trans start count | The number of transactions started by the tenant on this server. Each time a transaction is successfully started on the OBServer node where the session is created, the count is incremented. |
| 30006 | 4 | trans total used time | The cumulative time spent by the tenant on this server for transactions, measured in microseconds. Each time a transaction is completed on the OBServer node where the session is created, the time spent is added to this metric. |
| 30007 | 4 | trans commit count | The number of successful commit operations by the tenant on this server. Each time a transaction is successfully committed on the OBServer node where the session is connected, the count is incremented. |
| 30008 | 4 | trans commit time | The cumulative time spent by the tenant on this server for transaction commits, measured in microseconds. Each time a transaction is successfully committed on the OBServer node where the session is created, the commit time is added to this metric. |
| 30009 | 4 | trans rollback count | The number of successful rollback operations by the tenant on this server. Each time a transaction is successfully rolled back on the OBServer node where the session is created, the count is incremented. |
| 30010 | 4 | trans rollback time | The cumulative time spent by the tenant on this server for transaction rollbacks, measured in microseconds. Each time a transaction is successfully rolled back on the OBServer node where the session is created, the rollback time is added to this metric. |
| 30011 | 4 | trans timeout count | The number of timed-out transactions by the tenant on this server. Each time a transaction times out on the OBServer node where the session is created, the count is incremented. |
| 30012 | 4 | trans local trans count | The number of single-node transactions ended by the tenant on this server (including both commit and rollback). Each time a transaction is ended on the OBServer node where the session is created, the number of participants is checked. If the number of participants is 1, the count is incremented. |
| 30013 | 4 | trans distribute trans count | The number of distributed transactions ended by the tenant on this server (including both commit and rollback). Each time a transaction is ended on the OBServer node where the session is created, the number of participants is checked. If the number of participants is greater than 1, the count is incremented. |
| 30017 | 4 | trans without participant count | The number of read-only transactions ended by the tenant on this server (including both commit and rollback). Each time a transaction is ended on the OBServer node where the session is created, the number of participants is checked. If the number of participants is 0, the count is incremented. |
| 30018 | 4 | redo log replay count | The number of times redo logs of transactions have been replayed in the tenant. Each time a redo log of a transaction is replayed, the count is incremented. |
| 30019 | 4 | redo log replay time | The cumulative time spent by the tenant on this server for replaying redo logs of transactions, measured in microseconds. Each time a redo log is replayed, the time spent is added to this metric. |
| 30020 | 4 | prepare log replay count | The number of prepare logs of transactions that have been replayed in the tenant. Each time a prepare log of a transaction is replayed, the count is incremented. |
| 30021 | 4 | prepare log replay time | The cumulative time spent by the tenant on this server for replaying prepare logs of transactions, measured in microseconds. Each time a prepare log is replayed, the time spent is added to this metric. |
| 30022 | 4 | commit log replay count | The number of commit logs of transactions that have been replayed in the tenant. Each time a commit log of a transaction is replayed, the count is incremented. |
| 30023 | 4 | commit log replay time | The cumulative time spent by the tenant on this server for replaying commit logs of transactions. Each time a commit log is replayed, the time spent is added to this metric. |
| 30024 | 4 | abort log replay count | The number of abort logs of transactions that have been replayed in the tenant. Each time an abort log of a transaction is replayed, the count is incremented. |
| 30025 | 4 | abort log replay time | The cumulative time spent by the tenant on this server for replaying abort logs of transactions, measured in microseconds. Each time an abort log is replayed, the time spent is added to this metric. |
| 30026 | 4 | clear log replay count | The number of Clear logs replayed in the current tenant. The count increases by 1 each time a Clear log is replayed. |
| 30027 | 4 | clear log replay time | The cumulative time spent replaying Clear logs in the current tenant, in microseconds. The time spent on each replay is recorded and added to this metric. |
| 30053 | 4 | gts request total count | The total number of GTS requests processed by the GTS server. This count increases by 1 each time the GTS server processes a GTS request. |
| 30054 | 4 | gts acquire total time | The total waiting time for obtaining GTS in asynchronous scenarios, in microseconds. The waiting time increases when GTS is obtained. This feature is not yet implemented, so this metric is currently meaningless. |
| 30056 | 4 | gts acquire total wait count | The total number of GTS acquisitions in asynchronous scenarios. The count increases by 1 each time GTS is obtained. |
| 30063 | 4 | gts wait elapse total time | The total waiting time for GTS push in asynchronous scenarios, in microseconds. The waiting time increases when GTS is pushed. |
| 30065 | 4 | gts wait elapse total wait count | The total number of GTS push waits in asynchronous scenarios. The count increases by 1 each time GTS is pushed. |
| 30077 | 4 | trans early lock release enable count | This metric is deprecated starting from V4.4.1. |
| 30078 | 4 | trans early lock release unable count | This metric is deprecated starting from V4.4.1. |
| 30079 | 4 | read elr row count | The total number of rows where early row lock release occurred during MemTable writes. This count increases by 1 for each row where early row lock release was successful during MemTable writes. |
| 30080 | 4 | local trans total used time | The cumulative time spent on local transactions completed on the current machine (including both Commit and Rollback operations), in microseconds. This count increases by 1 for each transaction completed on the current machine, provided that the number of participants is 1. |
| 30081 | 4 | distributed trans total used time | The cumulative time spent on distributed transactions completed on the current machine (including both Commit and Rollback operations), in microseconds. This count increases by 1 for each transaction completed on the current machine, provided that the number of participants is greater than 1. |
| 30082 | 4 | tx data hit mini cache count | The number of times TxData was read from the MINI Cache. The MINI Cache is the fastest cache for TxData. A higher hit count indicates better performance. (The MINI Cache is request-level, with one per Access Context.) This count increases by 1 for each TxData read from the MINI Cache. |
| 30083 | 4 | tx data hit kv cache count | The number of times TxData was read from the KVCache. The KVCache is slightly slower than the MINI Cache. Most reads are expected to hit either the KVCache or the MINI Cache. This count increases by 1 for each TxData read from the KVCache. |
| 30084 | 4 | tx data read tx ctx count | The number of times TxData was read from the transaction context table. This count increases by 1 for each TxData read from the transaction context table. |
| 30085 | 4 | tx data read tx data memtable count | The number of times TxData was read from the Memtable of the transaction data table. This count increases by 1 for each TxData read from the Memtable of the transaction data table. |
| 30086 | 4 | tx data read tx data sstable count | The number of times TxData was read from the SSTable of the transaction data table. (Reading TxData from the SSTable is the slowest read operation, so this metric is expected to be low.) This count increases by 1 for each TxData read from the SSTable of the transaction data table. |
| 30200 | 4 | xa start total count | The total number of XA_START statements executed for XA transactions, including both successful and failed executions. This count increases by 1 after the XA_START logic is executed. |
| 30201 | 4 | xa start total used time | The total time spent executing XA_START statements for XA transactions, including both successful and failed executions, in microseconds. This time is added after the XA_START logic is executed. |
| 30202 | 4 | xa start with rpc total count | The total number of XA_START statements executed remotely for XA transactions, including only successful executions. This count increases by 1 after the XA_START logic is executed, provided that the XA_START was executed remotely and successfully. |
| 30203 | 4 | failed xa start total count | The total number of failed XA_START statements executed for XA transactions. This count increases by 1 after the XA_START logic is executed, provided that the execution failed. |
| 30204 | 4 | xa end total count | The total number of times the XA_END statement is executed for XA transactions, including both successful and failed executions. After the XA_END logic is executed on the transaction side, the count is incremented by 1. |
| 30205 | 4 | xa end total used count | The total time spent executing the XA_END statement for XA transactions, measured in microseconds. After the XA_END logic is executed on the transaction side, the local processing time is added to the count. |
| 30206 | 4 | xa end with rpc total count | The total number of successful remote executions of the XA_END statement for XA transactions. After the XA_END logic is executed on the transaction side, if the execution is remote and successful, the count is incremented by 1. |
| 30207 | 4 | failed xa end total count | The total number of failed executions of the XA_END statement for XA transactions. After the XA_END logic is executed on the transaction side, if an error occurs during execution, the count is incremented by 1. |
| 30208 | 4 | xa prepare total count | The total number of times the XA_PREPARE statement is executed for XA transactions, including both successful and failed executions. After the XA_PREPARE logic is executed on the transaction side, the count is incremented by 1. |
| 30209 | 4 | xa prepare total used time | The total time spent executing the XA_PREPARE statement for XA transactions, measured in microseconds. After the XA_PREPARE logic is executed on the transaction side, the local processing time is added to the count. |
| 30210 | 4 | xa prepare with rpc total count | The total number of successful remote executions of the XA_PREPARE statement for XA transactions. After the XA_START logic is executed on the transaction side, if the XA_PREPARE execution is remote and successful, the count is incremented by 1. |
| 30211 | 4 | failed xa prepare total count | The total number of failed executions of the XA_PREPARE statement for XA transactions. After the XA_PREPARE logic is executed on the transaction side, if an error occurs during execution, the count is incremented by 1. |
| 30212 | 4 | xa commit total count | The total number of times the XA_COMMIT statement is executed for XA transactions, including both successful and failed executions. After the XA_COMMIT logic is executed on the transaction side, the count is incremented by 1. |
| 30213 | 4 | xa commit total used time | The total time spent executing the XA_COMMIT statement for XA transactions, measured in microseconds. After the XA_COMMIT logic is executed on the transaction side, the local processing time is added to the count. |
| 30214 | 4 | xa commit with rpc total count | The total number of successful remote executions of the XA_COMMIT statement for XA transactions. After the XA_COMMIT logic is executed on the transaction side, if the execution is remote and successful, the count is incremented by 1. |
| 30215 | 4 | failed xa commit total count | The total number of failed executions of the XA_COMMIT statement for XA transactions. After the XA_COMMIT logic is executed on the transaction side, if an error occurs during execution, the count is incremented by 1. |
| 30216 | 4 | xa rollback total count | The total number of times the XA_ROLLBACK statement is executed for XA transactions, including both successful and failed executions. After the XA_ROLLBACK logic is executed on the transaction side, the count is incremented by 1. |
| 30217 | 4 | xa rollback total used time | The total time spent executing the XA_ROLLBACK statement for XA transactions, measured in microseconds. After the XA_ROLLBACK logic is executed on the transaction side, the local processing time is added to the count. |
| 30218 | 4 | xa rollback with rpc total count | The total number of successful remote executions of the XA_ROLLBACK statement for XA transactions. After the XA_START logic is executed on the transaction side, if the XA_ROLLBACK execution is remote and successful, the count is incremented by 1. |
| 30219 | 4 | failed xa rollback total count | The total number of failed executions of the XA_ROLLBACK statement for XA transactions. After the XA_ROLLBACK logic is executed on the transaction side, if an error occurs during execution, the count is incremented by 1. |
| 30220 | 4 | started xa trans count | The total number of successfully started XA transactions. After a XA transaction is successfully started on the transaction side, the count is incremented by 1. |
| 30221 | 4 | read only xa trans total count | The total number of read-only XA transactions. When submitting a XA transaction, if the transaction is read-only, the count is incremented by 1. |
| 30222 | 4 | xa trans with one phase commit total count | The total number of XA transactions that use one-phase commit. When submitting a XA transaction, if one-phase commit is used, the count is incremented by 1. |
| 30223 | 4 | inner sql total count in xa statement | The total number of INNER SQL statements executed during the execution of XA logic for XA transactions. When the XA logic is executed on the transaction side, the count is incremented by 1 after the INNER SQL is executed. |
| 30224 | 4 | total count of inner sql (latency >= 10ms) in xa statement | The total number of INNER SQL statements executed during the execution of XA logic for XA transactions that take more than 10 ms. When the XA logic is executed on the transaction side, if the INNER SQL execution time exceeds 10 ms, the count is incremented by 1. |
| 30225 | 4 | total count of inner sql (latency >= 20ms) in xa statement | The total number of INNER SQL statements executed during the execution of XA logic for XA transactions that take more than 20 ms. When the XA logic is executed on the transaction side, if the INNER SQL execution time exceeds 20 ms, the count is incremented by 1. |
| 30226 | 4 | inner sql total used time in xa statement | The total time consumed by INNER SQL statements in XA transactions, in microseconds. When an INNER SQL statement is executed during an XA transaction, the time consumed by the INNER SQL statement is added. |
| 30227 | 4 | inner rpc total count in xa statement | The total number of RPC calls in XA transactions. When an RPC call is made during an XA transaction, the count is incremented by 1. |
| 30228 | 4 | total count of inner rpc (latency >= 10ms) in xa statement | The total number of RPC calls in XA transactions that take more than 10 ms. When an RPC call takes more than 10 ms during an XA transaction, the count is incremented by 1. |
| 30229 | 4 | total count of inner rpc (latency >= 20ms) in xa statement | The total number of RPC calls in XA transactions that take more than 20 ms. When an RPC call takes more than 20 ms during an XA transaction, the count is incremented by 1. |
| 30230 | 4 | inner rpc total used time in xa statement | The total time consumed by RPC calls in XA transactions, in microseconds. When an RPC call is executed during an XA transaction, the time consumed by the RPC call is added. |
| 30231 | 4 | dblink trans total count | The total number of DBLink transactions. When a DBLink transaction is initiated, the count is incremented by 1. |
| 30232 | 4 | failed dblink trans total count | The total number of failed DBLink transactions. When a DBLink transaction is initiated and fails, the count is incremented by 1. |
| 30233 | 4 | dblink trans promotion total count | The total number of times a regular transaction is promoted to a DBLink transaction. When a regular transaction is promoted to a DBLink transaction, the count is incremented by 1. |
| 30234 | 4 | dblink trans callback total count | The total number of reverse link recovery calls in DBLink transactions. When a reverse link recovery call is executed during a DBLink transaction, the count is incremented by 1. |
| 30235 | 4 | dblink trans commit total count | The total number of DBLink transaction commits. When a DBLink transaction executes a commit statement, the count is incremented by 1. |
| 30236 | 4 | dblink trans commit total used time | The total time consumed by DBLink transaction commits, in microseconds. When a DBLink transaction executes a commit statement, the time consumed by the commit is added. |
| 30237 | 4 | failed dblink trans commit total count | The total number of failed DBLink transaction commits. When a DBLink transaction executes a commit statement and fails, the count is incremented by 1. |
| 30238 | 4 | dblink trans rollback total count | The total number of DBLink transaction rollbacks. When a DBLink transaction executes a rollback statement, the count is incremented by 1. |
| 30239 | 4 | dblink trans rollback total used time | The total time consumed by DBLink transaction rollbacks, in microseconds. When a DBLink transaction executes a rollback statement, the time consumed by the rollback is added. |
| 30240 | 4 | failed dblink trans rollback total count | The total number of failed DBLink transaction rollbacks. When a DBLink transaction executes a rollback statement and fails, the count is incremented by 1. |
SQL
| Column | Type | Nullable | Description |
|---|---|---|---|
| 40000 | 8 | sql select count | The number of times SQL SELECT statements are executed. |
| 40001 | 8 | sql select time | The total time spent on SQL SELECT statements, in microseconds. |
| 40002 | 8 | sql insert count | The number of INSERT statements issued by users. |
| 40003 | 8 | sql insert time | The total time spent on INSERT statements issued by users. |
| 40004 | 8 | sql replace count | The number of REPLACE statements issued by users. |
| 40005 | 8 | sql replace time | The total time spent on REPLACE statements issued by users. |
| 40006 | 8 | sql update count | The number of UPDATE statements issued by users. |
| 40007 | 8 | sql update time | The total time spent on UPDATE statements issued by users, in microseconds. |
| 40008 | 8 | sql delete count | The number of DELETE statements issued by users. |
| 40009 | 8 | sql delete time | The total time spent on DELETE statements issued by users, in microseconds. |
| 40010 | 8 | sql local count | The number of times SQL LOCAL statements are executed. |
| 40011 | 8 | sql remote count | The number of times SQL REMOTE statements are executed. |
| 40012 | 8 | sql distributed count | The number of times distributed SQL statements are executed. |
| 40013 | 8 | active sessions | The number of active sessions. Each new connection increases the count by 1, and each disconnected connection decreases it by 1. |
| 40014 | 8 | single query count | The total number of statements issued using the non-multiple query protocol. |
| 40015 | 8 | multiple query count | The total number of statements issued using the multiple query protocol. |
| 40016 | 8 | multiple query with one stmt count | The number of statements issued using the multiple query protocol, but containing only one SQL statement. |
| 40018 | 8 | sql other count | The number of times SQL statements other than SELECT/INSERT/REPLACE/UPDATE/DELETE/COMMIT/ROLLBACK are executed. |
| 40019 | 8 | sql other time | The total time spent on SQL statements other than SELECT/INSERT/REPLACE/UPDATE/DELETE/COMMIT/ROLLBACK, in microseconds. |
| 40020 | 8 | ps prepare count | The number of times the PREPARE operation is executed in PREPARE STATEMENT. |
| 40021 | 8 | ps prepare time | The total time spent on the PREPARE operation in PREPARE STATEMENT, in microseconds. |
| 40022 | 8 | ps execute count | The number of times the EXECUTE operation is executed in PREPARE STATEMENT. |
| 40023 | 8 | ps close count | The number of times the CLOSE operation is executed in PREPARE STATEMENT. |
| 40024 | 8 | ps close time | The total time spent on the CLOSE operation in PREPARE STATEMENT, in microseconds. |
| 40025 | 8 | sql commit count | The number of times the COMMIT operation is executed in SQL statements. |
| 40026 | 8 | sql commit time | The total time spent on the COMMIT operation, in microseconds. |
| 40027 | 8 | sql rollback count | The number of times the ROLLBACK operation is executed. |
| 40028 | 8 | sql rollback time | The total time spent on the ROLLBACK operation, in microseconds. |
| 40030 | 8 | opened cursors current | The number of cursors currently opened. The number of cursors currently opened. When a cursor is opened, the count increases by 1. When a cursor is closed, the count decreases by 1. |
| 40031 | 8 | opened cursors cumulative | The total number of cursors opened. The total number of cursors opened. When a cursor is opened, the count increases by 1. |
| 40102 | 8 | sql inner insert count | The total number of INSERT statements issued by INNER SQL1. |
| 40103 | 8 | sql inner insert time | The total time consumed by INSERT statements issued by INNER SQL, in microseconds1. |
| 40104 | 8 | sql inner replace count | The total number of REPLACE statements issued by INNER SQL1. |
| 40105 | 8 | sql inner replace time | The total time consumed by REPLACE statements issued by INNER SQL, in microseconds1. |
| 40106 | 8 | sql inner update count | The total number of UPDATE statements issued by INNER SQL1. |
| 40107 | 8 | sql inner update time | The total time consumed by UPDATE statements issued by INNER SQL, in microseconds1. |
| 40108 | 8 | sql inner delete count | The total number of DELETE statements issued by INNER SQL1. |
| 40109 | 8 | sql inner delete time | The total time consumed by DELETE statements issued by INNER SQL, in microseconds1. |
| 40112 | 8 | user logons cumulative | The total number of user logons. |
| 40113 | 8 | user logouts cumulative | The total number of user logouts. The count increases by 1 each time the session link is disconnected. |
| 40114 | 8 | user logons failed cumulative | The total number of failed user logons. The session establishment process fails when the user links to an OBServer node. |
| 40115 | 8 | user logons time cumulative | The total time consumed by user logons, in microseconds. The total time consumed by the session establishment process when the user logs in. |
| 40117 | 8 | sql remote execute time | The total time consumed by SQL REMOTE statements, in microseconds. The total time consumed by SQL REMOTE statements. |
| 40118 | 8 | sql distributed execute time | The total time consumed by distributed execution of SQL statements, in microseconds. The total time consumed by distributed execution, which is the sum of the time consumed by distributed execution. |
| 40119 | 8 | sql fail count | The number of failed SQL executions. |
| 40120 | 8 | inner sql local count | The number of INNER SQL LOCAL statements executed. |
| 40121 | 8 | inner sql remote count | The number of INNER SQL statements executed remotely. |
| 40122 | 8 | inner sql distributed count | The number of INNER SQL statements executed in a distributed manner. |
Note
Note 1: An INNER SQL statement is an SQL statement sent internally by OceanBase Database. It is typically used to query or modify internal tables.
Cache
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 50000 | 16 | row cache hit | The number of times the cache is hit when data rows are prefetched by the table get operator. In the lookup_in_cache function, if the data row is found in the cache, this metric is incremented by 1. |
| 50001 | 16 | row cache miss | The number of times the cache is not hit when data rows are prefetched by the table get operator. In the lookup_in_cache function, if the data row is not found in the cache, this metric is incremented by 1. |
| 50004 | 16 | bloom filter cache hit | The number of times the macroblock bloom filter cache is hit. This indicates that the SQL statement uses the built-in macroblock bloom filter2. |
| 50005 | 16 | bloom filter cache miss | The number of times the macroblock bloom filter cache is not hit. This indicates that the corresponding macroblock bloom filter is not built2. |
| 50006 | 16 | bloom filter filts | The number of effective filter passes of the macroblock bloom filter. This indicates that the corresponding row does not exist2. |
| 50007 | 16 | bloom filter passes | The number of filter passes of the macroblock bloom filter. This indicates that the corresponding row may exist2. |
| 50008 | 16 | block cache hit | The number of times the block cache is hit when microblocks are retrieved. In the process of retrieving microblocks, if the microblock is found in the cache, this metric is incremented by 1. |
| 50009 | 16 | block cache miss | The number of times the block cache is not hit when microblocks are retrieved. In the process of retrieving microblocks, if the microblock is not found in the cache, this metric is incremented by 1. |
| 50010 | 16 | location cache hit | The number of hits in the location cache. This includes hits in the ls_location_cache and tablet_ls_cache. When querying the mapping between tablets and logstreams or the location of a logstream, if valid data is successfully retrieved from the local cache, this metric is incremented by 1. This metric is triggered in the get method of ObTabletLSService and ObLSLocationService. |
| 50011 | 16 | location cache miss | The number of misses in the location cache. This includes misses in the ls_location_cache and tablet_ls_cache. When querying the mapping between tablets and logstreams or the location of a logstream, if valid data cannot be retrieved from the local cache (the cache does not exist, has expired, or is invalid), this metric is incremented by 1. In the get method of ObTabletLSService and ObLSLocationService, this metric is incremented by 1 when is_cache_hit is false. |
| 50012 | 16 | location cache wait | The number of times threads are blocked and wait for location information when the maximum number of concurrent requests is reached. When the maximum number of concurrent requests (max_count) is reached, threads need to wait on a semaphore. Each time a thread enters the waiting state in the ObLocationSem::acquire method, this metric is incremented by 1. This metric is triggered when has_wait is true, to control the concurrency of location information retrieval and prevent excessive concurrent requests from causing system pressure. |
| 50013 | 16 | location cache get hit from proxy virtual table | The number of hits in the location cache when querying tablet location information from the __all_virtual_proxy_schema view. When querying tablet location information from the proxy virtual table (ObAllVirtualProxySchema), if valid data is successfully retrieved from the cache, this metric is incremented by 1. |
| 50014 | 16 | location cache get miss from proxy virtual table | The number of misses in the location cache when querying tablet location information from the __all_virtual_proxy_schema view. When querying tablet location information from the proxy virtual table (ObAllVirtualProxySchema), if valid data cannot be retrieved from the cache (the cache does not exist, has expired, or is invalid), this metric is incremented by 1. |
| 50017 | 16 | location nonblock get hit | The number of non-blocking reads in the ls_location_cache and tablet_ls_cache. When using the nonblock_get method to query the mapping between tablets and logstreams or the location of a logstream, if valid data is successfully retrieved from the local cache, this metric is incremented by 1. In the ObTabletLSService::nonblock_get and ObLSLocationService::nonblock_get methods, this metric is triggered when OB_SUCC(ret) is true. Unlike the get method, the nonblock_get method does not wait for cache updates and immediately returns the result. |
| 50028 | 16 | kvcache sync wash time | The time consumed in synchronously flushing cache memory when memory is insufficient, in microseconds. When try_flush_washable_mb is called and cache flushing is performed, this metric is incremented by the corresponding time consumed. |
| 50029 | 16 | kvcache sync wash count | The number of times that cache is flushed to memory when memory is insufficient. This value increases by 1 when the try_flush_washable_mb function is called and cache is flushed. |
| 50033 | 16 | fuse row cache hit | The number of times that a row is read from the cache when the table get operator reads a row that is not in the memtable. The get_fuse_row_cache function checks whether the row corresponding to the rowkey is in the cache. If it is, this value increases by 1. |
| 50034 | 16 | fuse row cache miss | The number of times that a row is not read from the cache when the table get operator reads a row that is not in the memtable. The get_fuse_row_cache function checks whether the row corresponding to the rowkey is in the cache. If it is not, this value increases by 1. |
| 50035 | 16 | schema cache hit | The number of times that a schema is successfully retrieved from the schema cache. When a schema is queried, if the corresponding schema information is successfully retrieved from the local cache, this value increases by 1. In the ObSchemaCache::get_schema method, this value increases by 1 when cache_.get() is successfully called. |
| 50036 | 16 | schema cache miss | The number of times that a schema is not successfully retrieved from the schema cache. When a schema is queried, if the corresponding schema information cannot be retrieved from the local cache (the cache does not exist, has expired, or is invalid), this value increases by 1. In the ObSchemaCache::get_schema method, this value increases by 1 when cache_.get() fails. |
| 50037 | 16 | tablet ls cache hit | The number of times that a tablet is read from the cache. In the get_from_cache_ function, if the tablet is in the cache, this value increases by 1. |
| 50038 | 16 | tablet ls cache miss | The number of times that a tablet is not read from the cache. In the get_from_cache function, if the tablet is not in the cache, this value increases by 1. |
| 50045 | 16 | opt table stat cache hit | The hit rate of table-level or partition-level statistics cache. If the statistics are hit, the statistics are directly read from memory, and the unit is a percentage. KVCache tracks the hit rate of table-level or partition-level statistics cache. |
| 50046 | 16 | opt table stat cache miss | The miss rate of table-level or partition-level statistics cache. If the statistics are not hit, the statistics are loaded from the internal table to memory, and the unit is a percentage. KVCache tracks the miss rate of table-level or partition-level statistics cache. |
| 50047 | 16 | opt column stat cache hit | The hit rate of column-level statistics cache. If the statistics are hit, the statistics are directly read from memory, and the unit is a percentage. KVCache tracks the hit rate of column-level statistics cache. |
| 50048 | 16 | opt column stat cache miss | The miss rate of column-level statistics cache. If the statistics are not hit, the statistics are loaded from the internal table to memory, and the unit is a percentage. KVCache tracks the miss rate of column-level statistics cache. |
| 50049 | 16 | tmp page cache hit | The number of times that a page of a temporary file is read from the cache. On shared storage, temporary files do not use block cache but are organized into 8KB pages. Before reading data, KVCache is queried. If the data is hit, it is read from KVCache, and the hit count increases by 1. |
| 50050 | 16 | tmp page cache miss | The number of times that a page of a temporary file is not read from the cache. On shared storage, temporary files do not use block cache but are organized into 8KB pages. Before reading data, KVCache is queried. If the data is not hit, an I/O request is initiated, and the miss count increases by 1. |
| 50051 | 16 | tmp block cache hit | The number of times that a 2MB block of a temporary file is read from the cache. Before reading data from a temporary file on disk, the data is queried in KVCache. If the data is hit, it is read from the cache, and the hit count increases by 1. |
| 50052 | 16 | tmp block cache miss | The number of times that a block of a temporary file is not read from the cache. |
| 50055 | 16 | opt ds stat cache hit | The hit rate of dynamic sampling statistics cache. If the statistics are hit, the results are directly read from memory, and the unit is a percentage. KVCache tracks the hit rate of dynamic sampling statistics cache. |
| 50056 | 16 | opt ds stat cache miss | The miss rate of dynamic sampling statistics cache. If the statistics are not hit, a sampling SQL statement is initiated, and the unit is a percentage. KVCache tracks the miss rate of dynamic sampling statistics cache. |
| 50057 | 16 | storage meta cache hit | The number of times that secondary and tertiary metadata is read from the storage metadata cache. On a tablet that stores data, some large metadata (greater than 1K) is recorded, such as the schema of a table and multiple sstables. These metadata can be accessed on demand and do not need to be resident in memory. Therefore, we use KVCache to manage the memory lifecycle of these structures. These two metrics are the hit statistics of the metadata KVCache. |
| 50058 | 16 | storage meta cache miss | The number of times that secondary and tertiary metadata is not read from the storage metadata cache. On a tablet that stores data, some large metadata (greater than 1K) is recorded, such as the schema of a table and multiple sstables. These metadata can be accessed on demand and do not need to be resident in memory. Therefore, we use KVCache to manage the memory lifecycle of these structures. These two metrics are the hit statistics of the metadata KVCache. |
| 50059 | 16 | tablet cache hit | This view displays the number of times the tablet fragment cache is hit. A tablet is a data fragment that serves as a common structure in many processes. When a tenant supports a large number of partitions, the limited memory cannot guarantee that all tablets remain in memory. Therefore, we use KVCache to manage the memory lifecycle of tablets. These metrics indicate the cache hit rate for tablets. |
| 50060 | 16 | tablet cache miss | This view displays the number of times the tablet fragment cache is not hit. A tablet is a data fragment that serves as a common structure in many processes. When a tenant supports a large number of partitions, the limited memory cannot guarantee that all tablets remain in memory. Therefore, we use KVCache to manage the memory lifecycle of tablets. These metrics indicate the cache hit rate for tablets. |
| 50061 | 16 | schema history cache hit | This view displays the number of times the schema history cache is hit. The schema history cache stores the mapping between schema_type, tenant_id, schema_id, schema_version and precise_schema_version to avoid repeatedly querying the system table for the exact version number. If the corresponding exact schema version number is successfully retrieved from the history cache, the value is incremented by 1. |
| 50062 | 16 | schema history cache miss | This view displays the number of times the schema history cache is not hit. The schema history cache stores the mapping between schema_type, tenant_id, schema_id, schema_version and precise_schema_version to avoid repeatedly querying the system table for the exact version number. If the corresponding exact schema version number cannot be retrieved from the history cache (the cache does not exist, has expired, or is invalid), the value is incremented by 1. |
| 50063 | 16 | opt system stat cache hit | This view displays the cache hit rate for cost model system parameters. If the cache is hit, the value is incremented by 1. The unit is a percentage. KVCache statistics the cache hit rate for cost model parameters. |
| 50064 | 16 | opt system stat cache miss | This view displays the cache hit rate for cost model system parameters. If the cache is not hit, the value is incremented by 1. The unit is a percentage. KVCache statistics the cache miss rate for cost model parameters. |
| 50065 | 16 | log kv cache hit | This view displays the number of times the cold cache is hit. When reading logs from PALF, if the hot cache is not hit, the system attempts to read from the cold cache. If the log is found in the cold cache, the value is incremented by 1. |
| 50066 | 16 | log kv cache miss | This view displays the number of times the cold cache is not hit. When reading logs from PALF, if the hot cache is not hit, the system attempts to read from the cold cache. If the log is not found in the cold cache, the value is incremented by 1. |
| 50067 | 16 | data block cache miss | This view displays the number of times the block cache is not hit when reading data microblocks. When reading data microblocks, if the microblock is not found in the cache, the value is incremented by 1. |
| 50068 | 16 | index block cache miss | This view displays the number of times the block cache is not hit when reading intermediate index microblocks. When reading intermediate index microblocks, if the microblock is not found in the cache, the value is incremented by 1. |
| 50069 | 16 | multi version fuse row cache hit | This view displays the number of times the cache is hit when reading rows from a materialized view using the table get operator. In the get_fuse_row_cache function, if the table is a materialized view and the row corresponding to the rowkey is found in the cache, the value is incremented by 1. |
| 50070 | 16 | multi version fuse row cache miss | This view displays the number of times the cache is not hit when reading rows from a materialized view using the table get operator. In the get_fuse_row_cache function, if the table is a materialized view and the row corresponding to the rowkey is not found in the cache, the value is incremented by 1. |
| 50071 | 16 | backup index cache hit | This view displays the number of times the backup index cache is hit. The backup index is stored in the cache. During recovery, the system first reads the cache. If the data is not found in the cache, it reads from the backup medium. |
| 50072 | 16 | backup index cache miss | This view displays the number of times the backup index cache is not hit. The backup index is stored in the cache. During recovery, the system first reads the cache. If the data is not found in the cache, it reads from the backup medium. |
| 50073 | 16 | backup meta cache hit | This view displays the number of times the backup metadata cache is hit. The backup metadata is stored in the cache. During recovery, the system first reads the cache. If the data is not found in the cache, it reads from the backup medium. |
| 50074 | 16 | backup meta cache miss | This view displays the number of times the backup metadata cache is not hit. The backup metadata is stored in the cache. During recovery, the system first reads the cache. If the data is not found in the cache, it reads from the backup medium. |
| 50075 | 16 | truncate info cache hit | This view displays the number of times the truncate info cache is hit when reading truncate info. In the get_truncate_info_array function, if the truncate info is found in the cache, the value is incremented by 1. |
| 50076 | 16 | truncate info cache miss | This view displays the number of times the truncate info cache is not hit when reading truncate info. In the get_truncate_info_array function, if the truncate info is not found in the cache, the value is incremented by 1. |
| 120001 | 16 | tablet ls cache size | The cache size of a tablet, in bytes. The get_from_cache function uses the tablet cache. |
| 120002 | 16 | table stat cache size | The size of memory used for storing table-level or partition-level statistics, in bytes. The statistics are collected by the KVCache module. |
| 120003 | 16 | table col stat cache size | The size of memory used for storing column-level statistics, in bytes. The statistics are collected by the KVCache module. |
| 120004 | 16 | index block cache size | The size of the cache used for storing intermediate index microblocks, in bytes. The get_micro_block_handle function uses the index_block_cache_ cache. |
| 120006 | 16 | user block cache size | The size of the cache used for storing user microblocks, in bytes. The get_micro_block_handle function uses the index_block_cache_ cache. |
| 120008 | 16 | user row cache size | The size of the cache used for storing rows fetched by the table get operator, in bytes. The lookup_in_cache function uses this cache. |
| 120009 | 16 | bloom filter cache size | The total size of the bloom filter cache, in bytes. When users insert data, they need to check for primary key conflicts. To avoid I/O operations, a common performance optimization is to build a bloom filter for the data range. The following metrics are related to the bloom filter cache. |
| 120010 | 16 | log kv cache size | The size of logs read from the cold cache, in bytes. When reading logs from PALF, if the hot cache does not hit, it will attempt to read from the cold cache. If the log is found in the cold cache, the size of the log read from the cold cache is added to this metric. |
| 240001 | 16 | ss_micro_cache hit count | The total number of hits in the local microblock cache for all user requests in shared storage mode. When a user request needs to access microblock data and the data is retrieved from the local microblock cache, it is counted as a hit. |
| 240002 | 16 | ss_micro_cache miss count | The total number of misses in the local microblock cache for all user requests in shared storage mode. When a user request needs to access microblock data and the data is not retrieved from the local microblock cache, it is counted as a miss. |
| 240003 | 16 | ss_micro_cache failure count of adding cache | The total number of failures when attempting to add microblock data to the local microblock cache in shared storage mode. When adding microblock data to the local microblock cache fails, this metric is incremented. |
| 240004 | 16 | ss_micro_cache failure count of getting cache | The total number of failures when attempting to retrieve specified microblocks from the local microblock cache in shared storage mode. When retrieving specified microblock data from the local microblock cache fails, this metric is incremented (cache misses are not considered failures). |
| 240005 | 16 | ss_micro_cache major_compaction prewarm count | The number of successful attempts to add microblock data to the local microblock cache during major compaction prewarming in shared storage mode. During major compaction prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), this metric is incremented. |
| 240006 | 16 | ss_micro_cache migrate prewarm count | The number of successful attempts to add microblock data to the local microblock cache during migration prewarming in shared storage mode. During migration prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), this metric is incremented. |
| 240007 | 16 | ss_micro_cache replica prewarm count | The number of successful attempts to add microblock data to the local microblock cache during replica prewarming in shared storage mode. During replica prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), this metric is incremented. |
| 240008 | 16 | ss_micro_cache ddl prewarm count | The number of successful attempts to add microblock data to the local microblock cache during DDL prewarming in shared storage mode. During DDL prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), this metric is incremented. |
| 240009 | 16 | ss_micro_cache total hold micro_block count | The total number of microblock metadata (including valid and invalid metadata) held in the local microblock cache in shared storage mode. For each microblock added to the local microblock cache, a metadata entry is created in memory, called micro_meta. As microblock data expires or is evicted, it transitions from valid to invalid. This metric represents the total number of metadata entries in memory. |
| 240010 | 16 | ss_micro_cache total hold micro_block size | The total size of microblock data (including valid and invalid metadata) held in the local microblock cache in shared storage mode, in bytes. For each microblock added to the local microblock cache, a metadata entry is created in memory, called micro_meta. As microblock data expires or is evicted, it transitions from valid to invalid. This metric represents the total size of microblock data corresponding to all metadata entries in memory. |
| 240011 | 16 | ss_micro_cache hit total bytes | This view displays the total size of data that hit the local microblock cache on all nodes in shared storage mode, in bytes. When a user request requires accessing microblock data and the data is retrieved from the local microblock cache, it is considered a hit, and the micro_size value increases. |
| 240012 | 16 | ss_micro_cache miss total bytes | This view displays the total size of data that missed the local microblock cache on all nodes in shared storage mode, in bytes. When a user request requires accessing microblock data and the data is not retrieved from the local microblock cache, it is considered a miss, and the micro_size value increases. |
| 240013 | 16 | ss_micro_cache major_compaction prewarm bytes | This view displays the total size of microblocks successfully added to the local microblock cache during major compaction prewarming on all nodes in shared storage mode, in bytes. During major compaction prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), the micro_size value increases. |
| 240014 | 16 | ss_micro_cache migrate prewarm bytes | This view displays the total size of microblocks successfully added to the local microblock cache during migration replication or cross-AZ disaster recovery prewarming on all nodes in shared storage mode, in bytes. During migration replication or cross-AZ disaster recovery prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), the micro_size value increases. |
| 240015 | 16 | ss_micro_cache replica prewarm bytes | This view displays the total size of microblocks successfully added to the local microblock cache during leader/follower replica prewarming on all nodes in shared storage mode, in bytes. During leader/follower replica prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), the micro_size value increases. |
| 240016 | 16 | ss_micro_cache ddl prewarm bytes | This view displays the total size of microblocks successfully added to the local microblock cache during DDL prewarming on all nodes in shared storage mode, in bytes. During DDL prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), the micro_size value increases. |
| 240019 | 16 | ss_micro_cache total used disk size | This view displays the total size of used disk space in the local microblock cache on all nodes in shared storage mode, in bytes. The local microblock cache reserves a block of disk space by preallocating large files, which is logically divided into 2 MB data blocks. This view displays the total size of used data blocks. |
| 240024 | 16 | ss_micro_cache add micro_block count of common_io | This view displays the total number of microblocks added to the local microblock cache based on user requests on all nodes in shared storage mode. When a microblock is pulled from object storage based on a user request and cached to the local disk, this value increases by 1. |
| 240025 | 16 | ss_micro_cache get micro_block count of common_io | This view displays the total number of microblocks retrieved from the tenant's local microblock cache based on user requests on all nodes in shared storage mode. When a microblock is read from the local microblock cache based on a user request, this value increases by 1 (regardless of whether the read is successful). |
| 240026 | 16 | ss_micro_cache total new added micro_block count | This view displays the total number of microblocks added to the local microblock cache based on user requests on all nodes in shared storage mode. When a microblock needs to be added to the local microblock cache based on a user request and the microblock does not currently exist in the cache, it is considered the first addition, and the value increases by 1. |
| 240027 | 16 | ss_micro_cache new added micro_block count of common_io | This view displays the total number of microblocks successfully added to the tenant's local microblock cache based on user requests on all nodes in shared storage mode. When a microblock is successfully pulled from object storage based on a user request and cached to the local disk, and the cache does not contain any information about the microblock before the addition, this value increases by 1. |
| 240028 | 16 | ss_micro_cache total evicted micro_block count | This view displays the total number of ghost micro_meta entries accumulated in the local microblock cache on all nodes in shared storage mode. The local microblock cache uses the ARC cache replacement algorithm. When a microblock is evicted, its corresponding data is deleted, and the micro_meta becomes a ghost micro_meta. This view displays the total number of micro_meta entries that have been converted to ghost micro_meta. |
| 240029 | 16 | ss_micro_cache total deleted micro_block count | This view displays the total number of ghost micro_meta entries accumulated in the local microblock cache on all nodes in shared storage mode. The local microblock cache uses the ARC cache replacement algorithm. When a microblock is evicted, its corresponding micro_meta is retained as a ghost micro_meta. This view displays the total number of ghost micro_meta entries that have been deleted. |
| 240030 | 16 | ss_micro_cache released phy_block count by reorgan_task | This view displays the total number of data blocks net released by microblock reorganization tasks on all nodes in shared storage mode. The local microblock cache manages disk space in 2 MB data blocks. When the disk space is full, low-space-utilization data blocks are aggregated into new data blocks to release the space. This view displays the total number of net-released data blocks. |
| 240031 | 16 | ss_micro_cache storage_cache_policy prewarm count | This view displays the number of microblocks successfully added to the local microblock cache during manual hot data prewarming on all nodes in shared storage mode. During manual hot data prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), this value increases by 1. |
| 240032 | 16 | ss_micro_cache storage_cache_policy prewarm bytes | This view displays the total size of microblocks successfully added to the local microblock cache during manual hot data prewarming on all nodes in shared storage mode, in bytes. During manual hot data prewarming, hot microblock data is attempted to be added to the local microblock cache. If the microblock data is successfully added to the cache (even if it already exists), the micro_size value increases. |
| 245001 | 16 | ss_micro_cache micro_meta used memory size | This view displays the total size of memory consumed by microblock metadata in the local microblock cache on all nodes in shared storage mode, in bytes. This view displays the total size of memory consumed by microblock metadata in the local microblock cache. |
| 245002 | 16 | ss_micro_cache total alloc disk size | This view displays the disk space allocated to the local microblock cache in shared storage mode, in bytes. When initializing the local microblock cache module for a tenant, a disk space size is calculated and allocated to the local microblock cache. |
| 245011 | 16 | ss_micro_cache hot micro_block lack count | This view displays the number of missing microblock data entries in the local microblock cache in shared storage mode. Periodic tasks scan all microblocks in the KVCache and compare them with the local microblock cache. Each time a task runs, the value of this statistic starts at 0 and increases by 1 for each microblock that exists in the KVCache but not in the local microblock cache. |
| 245012 | 16 | ss_micro_cache read iops of common_io | This view displays the number of reads per second from the local microblock cache in shared storage mode based on user requests. It calculates the total number of attempts to read microblock data from the local microblock cache within 2 seconds based on user requests and then calculates the IOPS per second. |
| 245013 | 16 | ss_micro_cache read throughput of common_io | This view displays the amount of data read per second from the local microblock cache in shared storage mode based on user requests, in bytes. It calculates the total size of attempts to read microblock data from the local microblock cache within 2 seconds based on user requests and then calculates the THROUGHPUT per second. |
| 245014 | 16 | ss_micro_cache write iops of common_io | This view displays the number of writes per second to the local microblock cache in shared storage mode based on user requests. It calculates the total number of attempts to write microblock data to the local microblock cache within 2 seconds based on user requests and then calculates the IOPS per second. |
| 245015 | 16 | ss_micro_cache write throughput of common_io | This view displays the amount of data written per second to the local microblock cache in shared storage mode based on user requests, in bytes. It calculates the total size of attempts to write microblock data to the local microblock cache within 2 seconds based on user requests and then calculates the THROUGHPUT per second. |
| 245016 | 16 | ss_micro_cache read iops of prewarm_io | This view displays the number of reads per second from the local microblock cache in shared storage mode based on preheating requests. It calculates the total number of attempts to read microblock data from the local microblock cache within 2 seconds based on preheating requests and then calculates the IOPS per second. |
| 245017 | 16 | ss_micro_cache read throughput of prewarm_io | This view displays the amount of data read per second from the local microblock cache in shared storage mode based on preheating requests, in bytes. It calculates the total size of attempts to read microblock data from the local microblock cache within 2 seconds based on preheating requests and then calculates the THROUGHPUT per second. |
| 245018 | 16 | ss_micro_cache write iops of prewarm_io | This view displays the number of writes per second to the local microblock cache in shared storage mode based on preheating requests. It calculates the total number of attempts to write microblock data to the local microblock cache within 2 seconds based on preheating requests and then calculates the IOPS per second. |
| 245019 | 16 | ss_micro_cache write throughput of prewarm_io | This view displays the amount of data written per second to the local microblock cache in shared storage mode based on preheating requests, in bytes. It calculates the total size of attempts to write microblock data to the local microblock cache within 2 seconds based on preheating requests and then calculates the THROUGHPUT per second. |
| 245020 | 16 | ss_micro_cache valid micro_block count | This view displays the total number of valid microblocks in the local microblock cache in shared storage mode. The count is updated whenever microblock data is added to or evicted from the local microblock cache. |
| 245021 | 16 | ss_micro_cache valid micro_block size | This view displays the total size of valid microblock data in the local microblock cache in shared storage mode, in bytes. The size is updated whenever microblock data is added to or evicted from the local microblock cache. |
| 245022 | 16 | ss_macro_cache max capacity of the META_FILE type | This view displays the maximum disk cache capacity for Meta-type macroblocks in the macroblock cache in shared storage mode, in bytes3. |
| 245023 | 16 | ss_macro_cache META_FILE used disk size | This view displays the total disk size used by Meta-type macroblocks in the macroblock cache in shared storage mode, in bytes. It represents the total size of Meta-type macroblocks in the macroblock cache3. |
| 245024 | 16 | ss_macro_cache META_FILE hit count | This view displays the number of hits for Meta-type macroblocks in the macroblock cache in shared storage mode. Each time a macroblock is attempted to be retrieved from the macroblock cache, the hit/miss count is incremented based on the macroblock type3. |
| 245025 | 16 | ss_macro_cache META_FILE miss count | This view displays the number of misses for Meta-type macroblocks in the macroblock cache in shared storage mode. Each time a macroblock is attempted to be retrieved from the macroblock cache, the hit/miss count is incremented based on the macroblock type3. |
| 245026 | 16 | ss_macro_cache META_FILE hit bytes | This view displays the total size of hits for Meta-type macroblocks in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is attempted to be read from the macroblock cache, if the macroblock is found and it is a Meta-type macroblock, the size of the read data is added to this value3. |
| 245027 | 16 | ss_macro_cache META_FILE miss bytes | This view displays the total size of misses for Meta-type macroblocks in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is attempted to be read from the macroblock cache, if the macroblock is not found and it is a Meta-type macroblock, the size of the read data is added to this value3. |
| 245028 | 16 | ss_macro_cache max capacity of the TMP_FILE type | This view displays the maximum disk cache capacity for temporary file-type macroblocks in the macroblock cache in shared storage mode, in bytes. The macroblock cache supports cache evictions between different types, so this value is equal to the tenant's allocated macroblock cache disk size minus the reserved space3. |
| 245029 | 16 | ss_macro_cache TMP_FILE used disk size | This view displays the disk space occupied by temporary macroblocks in the macroblock cache in shared storage mode, in bytes. This value indicates the total size of temporary macroblocks in the macroblock cache3. |
| 245030 | 16 | ss_macro_cache TMP_FILE hit count | This view displays the number of hits for temporary macroblocks in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245031 | 16 | ss_macro_cache TMP_FILE miss count | This view displays the number of misses for temporary macroblocks in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245032 | 16 | ss_macro_cache TMP_FILE hit bytes | This view displays the total size of hits for temporary macroblocks in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the hit size is incremented based on the macroblock type3. |
| 245033 | 16 | ss_macro_cache TMP_FILE miss bytes | This view displays the total size of misses for temporary macroblocks in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the miss size is incremented based on the macroblock type3. |
| 245034 | 16 | ss_macro_cache max capacity of the MACRO_BLOCK type | This view displays the maximum disk cache capacity for macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. The cache capacities of different macroblock types can be shared, so this value is equal to the tenant's allocated macroblock cache disk size minus the reserved size3. |
| 245035 | 16 | ss_macro_cache MACRO_BLOCK used disk size | This view displays the disk space occupied by macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. This value indicates the total size of macroblocks of the MACRO_BLOCK type in the macroblock cache3. |
| 245036 | 16 | ss_macro_cache MACRO_BLOCK hit count | This view displays the number of hits for macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245037 | 16 | ss_macro_cache MACRO_BLOCK miss count | This view displays the number of misses for macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245038 | 16 | ss_macro_cache MACRO_BLOCK hit bytes | This view displays the total size of hits for macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the hit size is incremented based on the macroblock type3. |
| 245039 | 16 | ss_macro_cache MACRO_BLOCK miss bytes | This view displays the total size of misses for macroblocks of the MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the miss size is incremented based on the macroblock type3. |
| 245040 | 16 | ss_macro_cache max capacity of the HOT_TABLET_MACRO_BLOCK type | This view displays the maximum disk cache capacity for macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. The cache capacities of different macroblock types can be shared, so this value is equal to the tenant's allocated macroblock cache disk size minus the reserved size3. |
| 245041 | 16 | ss_macro_cache HOT_TABLET_MACRO_BLOCK used disk size | This view displays the disk space occupied by macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. This value indicates the total size of macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache3. |
| 245042 | 16 | ss_macro_cache HOT_TABLET_MACRO_BLOCK hit count | This view displays the number of hits for macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245043 | 16 | ss_macro_cache HOT_TABLET_MACRO_BLOCK miss count | This view displays the number of misses for macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode. Each time a macroblock is retrieved from the macroblock cache, the hit or miss count is incremented based on the macroblock type3. |
| 245044 | 16 | ss_macro_cache HOT_TABLET_MACRO_BLOCK hit bytes | This view displays the total size of hits for macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the hit size is incremented based on the macroblock type3. |
| 245045 | 16 | ss_macro_cache HOT_TABLET_MACRO_BLOCK miss bytes | This view displays the total size of misses for macroblocks of the HOT_TABLET_MACRO_BLOCK type in the macroblock cache in shared storage mode, in bytes. Each time a macroblock is retrieved from the macroblock cache, the miss size is incremented based on the macroblock type3. |
| 245046 | 16 | ss_macro_cache private macro hit count | This view displays the number of hits for macroblocks of the private type in the macroblock cache in shared storage mode3. |
| 245047 | 16 | ss_macro_cache private macro miss count | The number of misses of private macroblocks in the macroblock cache in shared storage mode. The hit or miss count is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245048 | 16 | ss_macro_cache private macro hit bytes | The total size of private macroblocks hit in the macroblock cache in shared storage mode, in bytes. The hit size is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245049 | 16 | ss_macro_cache private macro miss bytes | The total size of private macroblocks missed in the macroblock cache in shared storage mode, in bytes. The miss size is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245050 | 16 | ss_macro_cache shared macro hit count | The number of hits of shared macroblocks in the macroblock cache in shared storage mode. The hit or miss count is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245051 | 16 | ss_macro_cache shared macro miss count | The number of misses of shared macroblocks in the macroblock cache in shared storage mode. The hit or miss count is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245052 | 16 | ss_macro_cache shared macro hit bytes | The total size of shared macroblocks hit in the macroblock cache in shared storage mode, in bytes. The hit size is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245053 | 16 | ss_macro_cache shared macro miss bytes | The total size of shared macroblocks missed in the macroblock cache in shared storage mode, in bytes. The miss size is incremented based on the macroblock type each time a macroblock is retrieved from the macroblock cache3. |
| 245054 | 16 | external table disk cache hit count | The number of hits of macroblocks in the disk cache for external tables in both SN and SS modes. Each time a macroblock is hit in the disk cache for external tables, the value is incremented by 1. |
| 245055 | 16 | external table disk cache miss count | The number of misses of macroblocks in the disk cache for external tables in both SN and SS modes. Each time a macroblock is missed in the disk cache for external tables, the value is incremented by 1. |
| 245056 | 16 | external table disk cache hit bytes | The total size of macroblocks hit in the disk cache for external tables in both SN and SS modes, in bytes. Each time a macroblock is hit in the disk cache for external tables, the value is incremented by the size of the macroblock. |
| 245057 | 16 | external table disk cache miss bytes | The total size of macroblocks missed in the disk cache for external tables in both SN and SS modes, in bytes. Each time a macroblock is missed in the disk cache for external tables, the value is incremented by the size of the macroblock. |
| 245058 | 16 | ss_macro_cache total alloc disk size | The size of the disk space allocated to the local macroblock cache in shared storage mode, in bytes. When the local macroblock cache module is initialized for a tenant, a disk space size is allocated to the local macroblock cache. |
Note
- Note 2: When you insert data, the system checks for primary key conflicts. To avoid sending I/O requests, a common performance optimization technique is to build a Bloom filter for the data range. The following metrics are related to Bloom filter caching.
- Note 3: Macroblock caches are categorized into META, TMP_FILE, MACRO, and HOT_MACRO types. META caches store all meta-type macroblocks, and TMP_FILE caches store temporary file-type macroblocks. If a tablet is marked as a hot tablet, all its macroblocks are of the HOT_MACRO type. Other macroblocks are of the MACRO type. Different types of macroblock caches can occupy each other's space. Therefore, the value of this metric is the total macroblock cache disk size allocated to the tenant minus the reserved space.
Storage
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 60000 | 32 | io read count | The total IOPS of read I/O. This metric increases by 1 for each completed read I/O. |
| 60001 | 32 | io read delay | The total delay of read I/O, in microseconds. This metric accumulates the hardware service delay for each read I/O operation. The delay starts when the request is dispatched to the disk and ends when the disk completes processing and returns the result. |
| 60002 | 32 | io read bytes | The total bandwidth of read I/O. This metric tracks the total amount of read I/O, in bytes. You can calculate the average read I/O per second based on the change in this metric over a period of time. This metric accumulates the bandwidth of each completed read I/O. |
| 60003 | 32 | io write count | The total IOPS of write I/O. This metric increases by 1 for each completed write I/O. |
| 60004 | 32 | io write delay | The total delay of write I/O, in microseconds. This metric accumulates the hardware service delay for each write I/O operation. The delay starts when the request is dispatched to the disk and ends when the disk completes processing and returns the result. |
| 60005 | 32 | io write bytes | The total bandwidth of write I/O. This metric tracks the total amount of write I/O, in bytes. You can calculate the average write I/O per second based on the change in this metric over a period of time. This metric accumulates the bandwidth of each completed write I/O. |
| 60006 | 32 | memstore scan count | The number of range queries on MemTables. This metric increases by 1 when a range query on a MemTable starts. |
| 60007 | 32 | memstore scan succ count | The number of successful range queries on MemTables. This metric increases by 1 when a range query on a MemTable succeeds. |
| 60008 | 32 | memstore scan fail count | The number of failed range queries on MemTables. This metric increases by 1 when a range query on a MemTable fails for any reason. |
| 60009 | 32 | memstore get count | The number of point queries on MemTables. This metric increases by 1 when a point query on a MemTable starts. |
| 60010 | 32 | memstore get succ count | The number of successful point queries on MemTables. This metric increases by 1 when a point query on a MemTable succeeds. |
| 60011 | 32 | memstore get fail count | The number of failed point queries on MemTables. This metric increases by 1 when a point query on a MemTable fails for any reason. |
| 60012 | 32 | memstore apply count | The number of writes to MemTables. This metric increases by 1 when a write to a MemTable starts. |
| 60013 | 32 | memstore apply succ count | The number of successful writes to MemTables. This metric increases by 1 when a write to a MemTable succeeds. |
| 60014 | 32 | memstore apply fail count | The number of failed writes to MemTables. This metric increases by 1 when a write to a MemTable fails for any reason. |
| 60016 | 32 | memstore get time | The time consumed by point queries on MemTables, in microseconds. This metric increases by the time consumed by each point query on a MemTable, regardless of whether the query succeeds. |
| 60017 | 32 | memstore scan time | The time consumed by range queries on MemTables, in microseconds. This metric increases by the time consumed by each range query on a MemTable, regardless of whether the query succeeds. |
| 60018 | 32 | memstore apply time | The time consumed by writes to MemTables, in microseconds. This metric increases by the time consumed by each write to a MemTable, regardless of whether the write succeeds. |
| 60019 | 32 | memstore read lock succ count | The number of rows read successfully from MemTables. This metric increases by 1 for each successfully read row from a MemTable. |
| 60020 | 32 | memstore read lock fail count | The number of rows that failed to be read from MemTables due to read lock conflicts. This metric increases by 1 when a read lock conflict causes a timeout during a read operation on a MemTable. |
| 60021 | 32 | memstore write lock succ count | The number of rows written successfully to MemTables. This metric increases by 1 when a write to a MemTable succeeds.
NoteA write to a MemTable may still fail on an SSTable. |
| 60022 | 32 | memstore write lock fail count | The number of rows that fail to be written to the MemTable due to conflicts. During the MemTable write process, lock conflicts, lost updates, and primary key conflicts are checked. If any of these conflicts exist, the value increases by 1.
NoteThis does not include checks on SSTables. |
| 60023 | 32 | memstore wait write lock time | The total wait time for the MemTable write lock conflict, in microseconds. During the MemTable write process, if a lock conflict occurs, the request is placed in the lock conflict queue, and this value is increased by the time from when the request is placed in the queue until it is woken up. |
| 60024 | 32 | memstore wait read lock time | The total wait time for the MemTable read lock conflict, in microseconds. During the MemTable read process, if the data being read is in a committed state but the commit status and version number are not yet determined (for example, the data is in a pending commit log or distributed transaction state, which is a very short state), the read will wait on the read lock, and this value will be increased by the wait time. |
| 60027 | 32 | io prefetch micro block count | The total number of microblock cache I/O operations. During query path optimization, microblocks on the disk that need to be accessed are prefetched and loaded into memory, forming the microblock cache. This metric represents the total number of times the system loads microblocks from the disk. Combined with the microblock cache hit rate on internal tables, it can measure the effectiveness of query performance optimization. |
| 60028 | 32 | io prefetch micro block bytes | The total number of bytes of microblock cache I/O operations, in bytes. During query path optimization, microblocks on the disk that need to be accessed are prefetched and loaded into memory, forming the microblock cache. This metric represents the total number of bytes of microblocks loaded from the disk. Combined with the microblock cache hit rate on internal tables, it can measure the effectiveness of query performance optimization. |
| 60031 | 32 | storage read row count | The number of rows processed after fusing in the non-pushed-down path of the table scan operator, in rows. This value is incremented by 1 when the process_fuse_row function is called. |
| 60032 | 32 | storage delete row count | The number of effective rows actually deleted by DML statements. This value is incremented by 1 each time a row is deleted in the storage engine. |
| 60033 | 32 | storage insert row count | The number of effective rows actually inserted by DML statements. This value is incremented by 1 each time a row is inserted in the storage engine. |
| 60034 | 32 | storage update row count | The number of rows updated by update operations. This value is incremented by the number of rows updated when the update_rows function is called. |
| 60037 | 32 | memstore row purge count | Deprecated starting from V4.4.1. |
| 60038 | 32 | memstore row compaction count | The number of times sparse multi-versions on MemTable rows are compacted into a compact version. Sparse multi-versions on MemTable rows only record changed columns. When the number of multi-versions increases, the MemTable generates a compact single version to improve read performance. This value is incremented by 1 each time a compact single version is generated. |
| 60056 | 32 | memstore read row count | The number of rows read from the MemTable before filtering. This value is incremented by 1 each time a row is read from the MemTable. |
| 60057 | 32 | ssstore read row count | The number of rows read from major, minor, and mini SSTables in the pushed-down and non-pushed-down paths. In the pushed-down path, this includes filtered rows, equivalent to the total number of rows in the sstable within the range. For rowstore, this includes rows skipped by the skip index prefetch; for columnstore, it does not. In the non-pushed-down path, this includes filtered rows, excluding uncommitted, rolled back, and multi-version rows within microblocks. |
| 60058 | 32 | memstore write bytes | The amount of data successfully written to the MemTable, in bytes. After a successful MemTable write, the primary key and data size are recorded. |
| 60068 | 32 | memstore write lock wakenup count in lock_wait_mgr | The number of times the MemTable write lock conflict is woken up. During the MemTable write process, if a lock conflict occurs, the request is placed in the lock conflict queue. If the request is woken up, this value is incremented by 1. |
| 60077 | 32 | get row effect read | The number of effective rows read from microblocks by the table get operator. This value is incremented by 1 when the ObMicroBlockRowGetter::get_block_row function reads a row with a row flag that is not DF_NOT_EXIST. |
| 60078 | 32 | get row empty read | The number of invalid rows read from microblocks by the table get operator, in rows. This value is incremented by 1 when the ObMicroBlockRowGetter::get_block_row function reads a row with a row flag of DF_NOT_EXIST. |
| 60083 | 32 | memstore write lock wait timeout count | The number of times the MemTable write lock conflict timeout occurs without being woken up. During the MemTable write process, if a lock conflict occurs, the request is placed in the lock conflict queue. If the request times out before being woken up, this value is incremented by 1. |
| 60084 | 32 | accessed data micro block count by io | The number of microblocks that require I/O because they were not found in the cache. When accessing a data microblock, if it is not found in the cache and an I/O operation is executed, this value is incremented by 1. |
| 60085 | 32 | data micro block cache hit | The number of data microblocks found in the block cache. When accessing a data microblock, if it is found in the cache, this value is incremented by 1. |
| 60086 | 32 | accessed index micro block count by io | The number of microblocks accessed from the middle layer index that required I/O operations because they were not cached. This count increments by 1 each time a microblock is accessed from the middle layer index without being cached. |
| 60087 | 32 | index micro block cache hit | The number of microblocks accessed from the middle layer index that were cached. This count increments by 1 each time a microblock is accessed from the middle layer index and is found in the cache. |
| 60088 | 32 | blockscaned data micro block count | The number of microblocks opened in the push-down path, including skip index-prefetched microblocks for both rowstore and columnstore. For columnstore tables, the microblocks from multiple CGs are summed. The unit is microblocks. For rowstore: This count increments by 1 when a microblock is opened and the push-down path is available. For columnstore: This count increments by 1 when a microblock is opened in the push-down path. |
| 60089 | 32 | blockscaned row count | The total number of rows in the range covered by the microblocks opened in the push-down path. This includes filtered rows (which do not exist in the microblocks for rowstore or columnstore, such as uncommitted rows, rolled-back rows, or multi-versioned rows within the microblock). For rowstore, this includes rows skipped by the skip index, while for columnstore, it does not. For columnstore, the rows from multiple CGs are not summed. The unit is rows.
|
| 60090 | 32 | storage filtered row count | The total number of rows filtered by push-down or non-push-down filters. This count increments by the number of filtered rows during filtering. For rowstore, this includes rows skipped by the skip index, while for columnstore, it does not. |
| 60091 | 32 | minor ssstore read row count | The number of rows read from minor sstables and mini sstables in the push-down and non-push-down paths. The unit is rows. For the push-down path, this includes filtered rows, equivalent to the total number of rows in the range covered by the minor/mini sstables in the push-down path. For the non-push-down path, this includes filtered rows, excluding uncommitted rows, rolled-back rows, and multi-versioned rows within the microblock. |
| 60092 | 32 | major ssstore read row count | The number of rows read from major sstables in the push-down and non-push-down paths. The unit is rows. For the push-down path, this includes filtered rows, equivalent to the total number of rows in the range covered by the major sstables in the push-down path. For rowstore, this includes rows skipped by the skip index, while for columnstore, it does not. For the non-push-down path, this includes filtered rows, excluding uncommitted rows, rolled-back rows, and multi-versioned rows within the microblock. |
| 60093 | 32 | storage waiting throttle time | The total time spent throttling memory allocation to dynamically match the system's compaction speed. When the compaction speed lags behind the memory write speed, some modules' memory allocations are throttled. This configuration item records the total time spent throttling these memory allocations, in microseconds. After the memory usage of modules like MemTable (TxData, Mds) exceeds a certain threshold, each memory allocation causes the thread to sleep for a period, and the total sleep time is accumulated in this statistic. |
| 69000 | 32 | backup io read count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69001 | 32 | backup io read bytes | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69002 | 32 | backup io write count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69003 | 32 | backup io write bytes | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69010 | 32 | backup delete count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69012 | 32 | backup io read delay | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69013 | 32 | backup io write delay | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69017 | 32 | backup delete delay | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69019 | 32 | backup io list count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69020 | 32 | backup io read failed count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69021 | 32 | backup io write failed count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69022 | 32 | backup io delete failed count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69023 | 32 | backup io list failed count | This metric is deprecated starting from V4.4.1. Please check this metric in the I/O manager. |
| 69024 | 32 | backup io tagging count | This metric is deprecated starting with V4.4.1. Please check this metric in the I/O manager. |
| 69025 | 32 | backup io tagging failed count | This metric is deprecated starting with V4.4.1. Please check this metric in the I/O manager. |
| 130000 | 32 | active memstore used | The size of the active memstore on the node, in bytes. The node uses the memstore during replay or write operations. When the memstore usage reaches a certain level, it triggers a freeze. All unfrozen memstores are considered active. |
| 130001 | 32 | total memstore used | The total memory used by tenant memstores on the node, in bytes. This includes both active and frozen memstores, representing the total memory usage of all memstores for the tenant on the node. |
| 130002 | 32 | major freeze trigger | The size of the memstore that triggers a freeze, in bytes. This is calculated by adding memstore_freeze_trigger and max_cached_memstore_size in the get_tenant_memstore_cond function. |
| 130004 | 32 | memstore limit | The maximum memory available for tenant memstores on the node, in bytes. Users can set the maximum memory limit for tenants using memstore_limit_percentage and _memstore_limit_percentage. The former is at the cluster level, while the latter is at the tenant level. _memstore_limit_percentage takes precedence over memstore_limit_percentage. If neither is set, tenants with less than 8 GB of memory have a 40% memstore usage limit, and those with more than 8 GB have a 50% limit. |
| 240022 | 32 | object storage io head count | The count of HEAD operations for object storage. This count increases by 1 when a HEAD request is initiated for object storage. |
| 240023 | 32 | object storage io head fail count | The count of failed HEAD operations for object storage. This count increases by 1 when a HEAD request for object storage fails. |
Resources
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 140001 | 64 | min memory size | The memory specification of the tenant, which determines the memory upper limit of the tenant. The OmtNodeBalancer background thread periodically retrieves the latest min_memory from the DBA_OB_UNIT_CONFIGS table and updates it to the Limit of ObTenantMemoryMgr. |
| 140002 | 64 | max memory size | The memory specification of the tenant, which determines the memory upper limit of the tenant, in bytes. The OmtNodeBalancer background thread periodically retrieves the latest min_memory from the DBA_OB_UNIT_CONFIGS table and updates it to the Limit of ObTenantMemoryMgr. |
| 140003 | 64 | memory usage | The memory occupied by the tenant, in bytes. ObTenantMemoryMgr maintains a real-time memory value to record the actual memory occupied by the tenant. |
| 140004 | 64 | min cpus | The CPU specification of the tenant. It determines the number of resident worker threads of the tenant and the number of threads of some background modules. The OmtNodeBalancer background thread periodically retrieves the latest max_cpu from the DBA_OB_UNIT_CONFIGS table and synchronizes it to the multitenant system. The OmtNodeBalancer background thread periodically adjusts the number of worker threads based on the synchronized max_cpu. |
| 140005 | 64 | max cpus | The CPU specification of the tenant. It determines the number of resident worker threads of the tenant and the number of threads of some background modules. When cgroups are enabled, it determines the upper limit of the CPU usage rate of the tenant threads. The OmtNodeBalancer background thread periodically retrieves the latest max_cpu from the DBA_OB_UNIT_CONFIGS table and synchronizes it to the multitenant system. The OmtNodeBalancer background thread periodically adjusts the number of worker threads based on the synchronized max_cpu. |
| 140006 | 64 | cpu usage | The thread usage rate of the tenant worker threads, which reflects the busy level of the tenant worker threads, in percentage. The OmtNodeBalancer background thread statistics the ratio of the time spent by the tenant worker threads in processing requests to the total time every 10 seconds, normalizes the ratio, and multiplies it by the tenant min_cpu to obtain the cpu_usage value. |
| 140008 | 64 | observer memory used size | The actual memory used by the OBServer node, in bytes. AChunkMgr maintains a real-time memory value to record the actual memory used by the OBServer node (which is less than or equal to the actual memory occupied). |
| 140009 | 64 | observer memory free size | The chunk cache of the OBServer node. AChunkMgr maintains a real-time memory value to record the cache size of the OBServer node. The cache represents the size of the memory allocated to the OBServer node but not actually used. |
| 140010 | 64 | is mini mode | Indicates whether the OBServer node process is in mini mode. If the memory of the OBServer node is less than 12 GB, it is considered to be in mini mode. |
| 140011 | 64 | observer memory hold size | The memory occupied by the OBServer node, including the cache and all user-actually-used memory, in bytes. AChunkMgr maintains a real-time memory value to record the memory occupied by the OBServer node. |
| 140012 | 64 | worker time | The total busy time of the tenant worker threads, in microseconds. The OmtNodeBalancer background thread statistics the total time spent by the tenant worker threads in processing requests every 10 seconds and accumulates it into the worker_time value. |
| 140013 | 64 | cpu time | The total CPU time used by the tenant worker threads and background threads, in microseconds.
|
| 140014 | 64 | effective observer memory limit | The memory upper limit of the OBServer node, in bytes. Only the sys tenant can query this value, which is at the node level.
|
| 140015 | 64 | effective system memory | The reserved memory of the 500 tenant and the hidden sys memory, in bytes. By default, it is adaptively set based on the memory_limit configuration parameter. You can also explicitly specify it by using the system_memory configuration parameter. |
| 140016 | 64 | effective hidden sys memory | The memory upper limit of the hidden sys tenant, in bytes. Each OBServer node allocates a portion of memory for the sys tenant. By default, it is adaptively set based on the system_memory configuration parameter. You can also explicitly specify it by using the _hidden_sys_tenant_memory configuration parameter. |
| 140017 | 64 | max session num | The maximum number of sessions allowed for the tenant. The maximum number of sessions allowed for the tenant is calculated based on the memory size of the tenant. |
| 140018 | 64 | kvcache hold | The size of memory occupied by the KVCache, in bytes. The memory manager tracks the memory occupied by the KVCache. |
| 140019 | 64 | unmanaged memory size | The size of memory directly read from mmap by the library function, in bytes. This is a global memory value that records in real time the memory applied by the library function through mmap/unmap. It refers to the memory applied by the third-party library function called on the OBServer node. |
| 140020 | 64 | hidden sys data disk size | The size of the disk configured for the sys tenant in shared storage mode, in bytes.
|
Logs
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 70000 | 128 | refresh schema count | The number of times that the schema is successfully refreshed. When OceanBase Database needs to refresh the schema, the value is incremented each time the schema is successfully refreshed. This is implemented in the ObServerSchemaService::refresh_schema method. The operation includes two modes: full refresh refresh_full_schema and incremental refresh refresh_increment_schema, which are used to maintain consistency between the local metadata cache and the system tables. |
| 70001 | 128 | refresh schema time | The total time consumed in successfully refreshing the schema, in microseconds. When OceanBase Database refreshes the schema, the total time consumed in the entire refresh process is recorded. In the ObServerSchemaService::refresh_schema method, when OB_SUCC(ret) is True, the time difference from the start to the end of the method is accumulated. This includes the time consumed in both the full refresh refresh_full_schema and incremental refresh refresh_increment_schema modes. |
| 70002 | 128 | inner sql connection execute count | The number of INNER SQL statements executed. The count is incremented each time an INNER SQL statement is executed. |
| 70003 | 128 | inner sql connection execute time | The total time consumed in executing INNER SQL statements, in microseconds. The total time consumed in executing INNER SQL statements is accumulated. |
| 70006 | 128 | log stream table operator get count | The number of times that the loaded LS information is successfully read from the __all_ls_meta_table table. When the ObLSTableOperator reads log stream information from the __all_ls_meta_table table, the value is incremented each time the ls_info is successfully retrieved. This is implemented in the ObLSTableOperator::get method. The operator supports retrieving log stream information from memory, RPC, or persistent tables, which is used for position caching and metadata management. |
| 70007 | 128 | log stream table operator get time | The total time consumed in successfully reading the loaded LS information from the __all_ls_meta_table table, in microseconds. When the ObLSTableOperator reads log stream information from the __all_ls_meta_table table, the total time consumed in the entire retrieval process is recorded. In the ObLSTableOperator::get method, the time difference from the start to the end of the method is accumulated. This includes the time consumed in retrieving log stream information from memory, RPC, or persistent tables. |
| 160001 | 128 | oblogger log bytes | The total size of logs printed, in bytes. This refers to the output printing process of system logs such as observer.log. |
| 160002 | 128 | election log bytes | The total size of election logs printed, in bytes. This refers to the accumulated size of election.log logs. |
| 160004 | 128 | oblogger total log count | The number of times that logs are printed. This refers to the output printing process of system logs such as observer.log. |
| 160019 | 128 | async error log dropped count | The number of times that ERROR logs fail to be printed (due to throttling, for example). This refers to the output printing process of system logs such as observer.log. |
| 160020 | 128 | async warn log dropped count | The number of times that WARN logs fail to be printed. This refers to the output printing process of system logs such as observer.log. |
| 160021 | 128 | async info log dropped count | The number of times that INFO logs fail to be printed (due to throttling, for example). This refers to the output printing process of system logs such as observer.log. |
| 160022 | 128 | async trace log dropped count | The number of times that TRACE logs fail to be printed. This refers to the output printing process of system logs such as observer.log. |
| 160023 | 128 | async debug log dropped count | The number of times that DEBUG logs fail to be printed (due to throttling, for example). This refers to the output printing process of system logs such as observer.log. |
| 160024 | 128 | async log flush speed | The average number of logs written per second. This refers to the output printing process of system logs such as observer.log. |
| 160025 | 128 | async generic log write count | The number of times that default logs are successfully printed. This refers to the output printing process of system logs such as observer.log. |
| 160026 | 128 | async user request log write count | This metric is deprecated and is retained only in the code. This refers to the output printing process of system logs such as observer.log. |
| 160027 | 128 | async data maintain log write count | The number of times that log printing for major compactions is successful. This refers to the output printing process of system logs such as observer.log. |
| 160028 | 128 | async root service log write count | The number of times that RS logs are successfully printed. This refers to the output printing process of system logs such as observer.log. |
| 160029 | 128 | async schema log write count | The number of times that schema logs fail to be printed (due to throttling, for example). This refers to the output printing process of system logs such as observer.log. |
| 160030 | 128 | async force allow log write count | The number of times asynchronous force allow log writes are successful. This refers to the process of outputting system logs such as observer.log. |
| 160031 | 128 | async generic log dropped count | The number of times asynchronous generic log writes are dropped due to reasons such as throttling. This refers to the process of outputting system logs such as observer.log. |
| 160032 | 128 | async user request log dropped count | This parameter is deprecated and is retained only in the code. This refers to the process of outputting system logs such as observer.log. |
| 160033 | 128 | async data maintain log dropped count | The number of times asynchronous data maintenance log writes are dropped due to reasons such as throttling. This refers to the process of outputting system logs such as observer.log. |
| 160034 | 128 | async root service log dropped count | The number of times asynchronous root service log writes are dropped due to reasons such as throttling. This refers to the process of outputting system logs such as observer.log. |
| 160035 | 128 | async schema log dropped count | The number of times asynchronous schema log writes are dropped due to reasons such as throttling. This refers to the process of outputting system logs such as observer.log. |
| 160036 | 128 | async force allow log dropped count | The number of times asynchronous force allow log writes are dropped due to reasons such as throttling. This refers to the process of outputting system logs such as observer.log. |
CLOG
| Item ID | Item Type | Item Name | Description |
|---|---|---|---|
| 80001 | 256 | palf write io count to disk | The number of times that clogs are written to disk. This value is incremented by 1 each time a clog is successfully written to disk. |
| 80002 | 256 | palf write size to disk | The size of clogs written to disk, in bytes. This value is incremented by the size of the clog that is successfully written to disk. |
| 80003 | 256 | palf write total time to disk | The total time taken to write clogs to disk, in microseconds. This value is incremented by the time taken to write the clog to disk. |
| 80004 | 256 | palf read count from hot cache | The number of times that clogs are read from the hot cache. This value is incremented by 1 each time a clog is read from the hot cache. |
| 80005 | 256 | palf read size from hot cache | The size of clogs read from the hot cache, in bytes. This value is incremented by the size of the clog that is read from the hot cache. |
| 80006 | 256 | palf read total time from hot cache | The total time taken to read clogs from the hot cache, in microseconds. This value is incremented by the time taken to read the clog from the hot cache. |
| 80007 | 256 | palf read io count from disk | The number of times that clogs are read from disk. This value is incremented by 1 each time a clog is successfully read from disk. |
| 80008 | 256 | palf read size from disk | The size of clogs read from disk, in bytes. This value is incremented by the size of the clog that is successfully read from disk. |
| 80009 | 256 | palf read total time from disk | The total time taken to read clogs from disk, in microseconds. This value is incremented by the time taken to read the clog from disk. |
| 80010 | 256 | palf handle rpc request count | The number of RPCs processed by the PALF layer. This value is incremented by 1 each time an RPC is processed by the PALF layer. |
| 80011 | 256 | archive read log size | The total size of clogs read by the log archiving module, in bytes. This value is incremented by the size of clogs read by the log archiving module within a 10-second interval. |
| 80012 | 256 | archive write log size | The total size of clogs written to the archiving medium by the log archiving module, in bytes. This value is incremented by the size of clogs written to the archiving medium by the log archiving module within a 10-second interval. |
| 80013 | 256 | restore read log size | The total size of clogs read by the log restore module, in bytes. This value is incremented by the size of clogs read by the log restore module each time it triggers a remote log read. |
| 80014 | 256 | restore write log size | The total size of clogs submitted by the log restore module, in bytes. This value is incremented by the size of clogs submitted by the log restore module each time it triggers a log submission. |
| 80057 | 256 | clog trans log total size | The total size of data committed to the PALF layer, in bytes. This value is incremented by the size of the log committed to the PALF layer. |
| 80058 | 256 | log storage compress original size | The original size of logs submitted to the PALF layer before compression, in bytes. This value is incremented by the size of logs submitted to the PALF layer before compression when log compression is enabled. |
| 80059 | 256 | log storage compress compressed size | The compressed size of logs submitted to the PALF layer, in bytes. This value is incremented by the size of logs submitted to the PALF layer after compression when log compression is enabled. |
| 81001 | 256 | external log service fetch log size | The size of logs fetched from this node by the log synchronization link (such as OBCDC or a remote standby database), in bytes. This value is incremented by the size of logs returned by each RPC sent by a downstream synchronization link. |
| 81002 | 256 | external log service fetch log count | The number of logs fetched from this node by the log synchronization link (such as OBCDC or a remote standby database). This value is incremented by the number of logs returned by each RPC sent by a downstream synchronization link. |
| 81003 | 256 | external log service fetch rpc count | The number of RPCs sent by the log synchronization link (such as OBCDC or a remote standby database) to fetch logs from this node. This value is incremented by 1 each time an RPC is sent by a downstream synchronization link. |
Root Service
| Monitor Item ID | Monitor Item Type | Monitor Item Name | Description |
|---|---|---|---|
| 110015 | 2048 | success rpc process | The number of RPC requests successfully processed by Root Service. The count increases by 1 each time Root Service successfully processes an RPC request. This includes all RPC requests sent to Root Service and executed successfully. |
| 110016 | 2048 | failed rpc process | The number of RPC requests that failed to be processed by Root Service. The count increases by 1 each time Root Service fails to process an RPC request. This includes all RPC requests sent to Root Service but executed failed. |
| 110017 | 2048 | balancer succ execute count | The number of times the load balancer in Root Service successfully executes unit balancing. The count increases by 1 each time the load balancer in Root Service successfully executes a unit balancing operation. |
| 110018 | 2048 | balancer failed execute count | The number of times the load balancer in Root Service failed to execute unit balancing. The count increases by 1 each time the load balancer in Root Service fails to execute a unit balancing operation. |
ASH
| Monitoring item ID | Monitoring item type | Monitoring item name | Description |
|---|---|---|---|
| 200001 | 3072 | DB time | The total time spent by foreground processes on database operations, including CPU time and non-idle wait time, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200002 | 3072 | DB CPU | The total CPU time consumed by foreground processes, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200005 | 3072 | background elapsed time | The total time spent by background processes on database operations, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200006 | 3072 | background cpu time | The total CPU time consumed by background processes, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200010 | 3072 | non idle wait time | The total non-idle wait time of foreground processes, measured in microseconds. This is the total time when sessions are waiting but not in idle wait mode. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200011 | 3072 | idle wait time | The total idle wait time of foreground processes, measured in microseconds. This is the total time when sessions are in idle wait mode. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200012 | 3072 | background database time | The total time spent by background processes on database operations, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200013 | 3072 | background database non-idle wait time | The total non-idle wait time of background processes on database operations, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200014 | 3072 | background database idle wait time | The total idle wait time of background processes on database operations, measured in microseconds. OceanBase Database periodically updates the Time Model statistics. When a thread is active, it is either in the ON_CPU state or waiting for an event. The Time Model statistics are accumulated based on the duration spent in each state. |
| 200015 | 3072 | diagnostic info object allocated count | The total number of diagnostic objects allocated. Diagnostic objects on OBServer nodes are used to store diagnostic statistics of database foreground and background tasks (such as SQL and RPC tasks). These objects are typically allocated at the start of a task and deallocated at the end. |
| 200016 | 3072 | diagnostic info object allocate failure count | The total number of diagnostic object allocation failures. Diagnostic objects on OBServer nodes are used to store diagnostic statistics of database foreground and background tasks (such as SQL and RPC tasks). These objects are typically allocated at the start of a task and deallocated at the end. |
| 200017 | 3072 | diagnostic info object returned count | The total number of diagnostic objects deallocated. Diagnostic objects on OBServer nodes are used to store diagnostic statistics of database foreground and background tasks (such as SQL and RPC tasks). These objects are typically allocated at the start of a task and deallocated at the end. |
| 200018 | 3072 | diagnostic info object return failure count | The total number of diagnostic object deallocation failures. Diagnostic objects on OBServer nodes are used to store diagnostic statistics of database foreground and background tasks (such as SQL and RPC tasks). These objects are typically allocated at the start of a task and deallocated at the end. |
| 220001 | 3072 | concurrency wait total time | The total wait time caused by concurrency wait events, such as resource locking, measured in microseconds. This is the accumulated sum of corresponding wait events in OceanBase Database. |
| 220002 | 3072 | user io wait total time | The total time spent by user processes waiting for I/O operations (such as reading or writing data to disk) to complete, measured in microseconds. This is the accumulated sum of corresponding wait events in OceanBase Database. |
| 220003 | 3072 | application wait total time | The total wait time caused by user application code, such as lock waits due to row-level locks or explicit lock commands, measured in microseconds. This is the accumulated sum of corresponding wait events in OceanBase Database. |
| 220004 | 3072 | schedule wait total time | The total time consumed by wait events in the SCHEDULER category, in microseconds. This value is the sum of the corresponding wait events in OceanBase Database. |
| 220005 | 3072 | network wait total time | The total time consumed by wait events in the network category, in microseconds. This value is the sum of the corresponding wait events in OceanBase Database. |
TableAPI
For more information about the TableAPI metrics, see OBKV-Table metrics in the OBKV documentation.
WR
| Metric ID | Metric Type | Metric Name | Description |
|---|---|---|---|
| 210001 | 8192 | wr snapshot task elapse time | The total time spent in collecting a WR snapshot, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210002 | 8192 | wr snapshot task cpu time | The total CPU time spent in collecting a WR snapshot, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210003 | 8192 | wr purge task elapse time | The total time spent in purging a WR snapshot, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210004 | 8192 | wr purge task cpu time | The total CPU time spent in purging a WR snapshot, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210005 | 8192 | wr schedular elapse time | The total time spent in scheduling a WR task, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210006 | 8192 | wr schedular cpu time | The total CPU time spent in scheduling a WR task, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210007 | 8192 | wr user submit snapshot elapse time | The total time spent in collecting a WR snapshot initiated by a user, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210008 | 8192 | wr user submit snapshot cpu time | The total CPU time spent in collecting a WR snapshot initiated by a user, in microseconds. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210009 | 8192 | wr collected active session history row count | The total number of rows collected in the ASH (ob_active_session_history) table, in rows. The WR periodically collects internal views of OceanBase Database to record the system status and provides relevant views for users to display and manage the DBMS_WORKLOAD_REPOSITORY package. |
| 210010 | 8192 | ash schedular elapse time | The total time spent in sampling ASH data, in microseconds. ASH is a diagnostic mechanism that samples and records the running status of all active sessions in OceanBase Database. The ASH sampling thread samples and records the running status of active sessions every second. |
| 210011 | 8192 | ash schedular cpu time | The total CPU time spent in sampling ASH data, in microseconds. ASH is a diagnostic mechanism that samples and records the running status of all active sessions in OceanBase Database. The ASH sampling thread samples and records the running status of active sessions every second. |
References
For more information about the monitoring items, see Overview of system monitoring metrics.