On this page
The Overview metrics let you monitor SQL performance. For Basic deployments, you can also monitor Request Units. For Basic and Standard deployments, you can also monitor storage.
To view these graphs, select a cluster from the Clusters page, and click Metrics in the Monitoring section of the left side navigation. On the Metrics page, click the Overview tab.
Time interval selection
The time interval selector at the top of each tab allows you to filter the view for a predefined or custom time interval. Use the navigation buttons to move to the previous, next, or current time interval. When you select a time interval, the same interval is selected for all charts on the Metrics page.
SQL Connections
Short Name |
CockroachDB Metric Name |
Description |
Usage |
Connections Per Second |
sql.new_conns
|
Number of SQL connections created |
The rate of this metric shows how frequently new connections are being established. This can be useful in determining if a high rate of incoming new connections is causing additional load on the server due to a misconfigured application. |
SQL Statements
Short Name |
CockroachDB Metric Name |
Description |
Usage |
Select |
sql.select.count
|
Number of SQL SELECT statements successfully executed |
This high-level metric reflects workload volume. Monitor this metric to identify abnormal application behavior or patterns over time. If abnormal patterns emerge, apply the metric's time range to the SQL Activity pages to investigate interesting outliers or patterns. For example, on the Transactions page and the Statements page, sort by the Execution Count column. To find problematic sessions, on the Sessions page, sort by the Transaction Count column. Find the sessions with high transaction counts and trace back to a user or application. |
Update |
sql.update.count
|
Number of SQL UPDATE statements successfully executed |
This high-level metric reflects workload volume. Monitor this metric to identify abnormal application behavior or patterns over time. If abnormal patterns emerge, apply the metric's time range to the SQL Activity pages to investigate interesting outliers or patterns. For example, on the Transactions page and the Statements page, sort by the Execution Count column. To find problematic sessions, on the Sessions page, sort by the Transaction Count column. Find the sessions with high transaction counts and trace back to a user or application. |
Insert |
sql.insert.count
|
Number of SQL INSERT statements successfully executed |
This high-level metric reflects workload volume. Monitor this metric to identify abnormal application behavior or patterns over time. If abnormal patterns emerge, apply the metric's time range to the SQL Activity pages to investigate interesting outliers or patterns. For example, on the Transactions page and the Statements page, sort by the Execution Count column. To find problematic sessions, on the Sessions page, sort by the Transaction Count column. Find the sessions with high transaction counts and trace back to a user or application. |
Delete |
sql.delete.count
|
Number of SQL DELETE statements successfully executed |
This high-level metric reflects workload volume. Monitor this metric to identify abnormal application behavior or patterns over time. If abnormal patterns emerge, apply the metric's time range to the SQL Activity pages to investigate interesting outliers or patterns. For example, on the Transactions page and the Statements page, sort by the Execution Count column. To find problematic sessions, on the Sessions page, sort by the Transaction Count column. Find the sessions with high transaction counts and trace back to a user or application. |
Service Latency: SQL Statements
Short Name |
CockroachDB Metric Name |
Description |
Usage |
P90, P99, P99.9, P99.99 |
sql.service.latency
|
Latency of SQL request execution |
These high-level metrics reflect workload performance. Monitor these metrics to understand latency over time. If abnormal patterns emerge, apply the metric's time range to the SQL Activity pages to investigate interesting outliers or patterns. The Statements page has P90 Latency and P99 latency columns to enable correlation with this metric. |
Request Units
Short Name |
CockroachDB Metric Name |
Description |
Usage |
RU, Average RUs |
tenant.consumption.request_units
|
Total RU consumption |
The CPU and I/O resources being used by queries in the cluster. Simple queries consume few RUs, while complicated queries with many reads and writes consume more RUs. To learn more about how RUs are calculated, refer to Resource Usage. |
Storage
Short Name |
CockroachDB Metric Name |
Description |
Usage |
Storage usage |
livebytes
|
Number of bytes of live data (keys plus values) |
The amount of data being stored in the cluster. In the Storage Used graph, this is the logical number of live bytes and does not account for compression or replication. |
See also
Was this helpful?