Skip to main content
The Storage dashboard lets you monitor the storage utilization of your cluster. To view this dashboard, , click Metrics in the left-hand navigation, and select Dashboard > Storage.

​
Dashboard navigation

Use the Graph menu to display metrics for your entire cluster or for a specific node. To the right of the Graph and Dashboard menus, a time interval selector 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 in the pages. However, if you select 10 or 30 minutes, the interval defaults to 1 hour in SQL Activity pages. When viewing graphs, a tooltip will appear at your mouse cursor providing further insight into the data under the mouse cursor. Click anywhere within the graph to pin the tooltip in place, decoupling the tooltip from your mouse movements. Click anywhere within the graph to cause the tooltip to follow your mouse once more. The Storage dashboard displays the following time series graphs:

​
Capacity

You can monitor the Capacity graph to determine when additional storage is needed (e.g., by ). DB Console Capacity graph Expected values for a healthy cluster: Used capacity should not persistently exceed 80% of the total capacity. For instructions on how to free up disk space as quickly as possible after dropping a table, see

​
Capacity metrics

The Capacity graph displays disk usage by CockroachDB data in relation to the maximum size, which is determined as follows:
  • If a store size was specified using the flag when starting nodes, this value is used as the limit for CockroachDB data.
  • If no store size has been explicitly set, the actual disk capacity is used as the limit for CockroachDB data.
The available capacity thus equals the amount of empty disk space, up to the value of the maximum store size. The used capacity refers only to disk space occupied by CockroachDB data, which resides in the store directory on each node. The disk usage of the Cockroach binary, operating system, and other system files is not shown on the Capacity graph. If you are testing your deployment locally with multiple CockroachDB nodes running on a single machine (this is ), you must explicitly per node in order to display the correct capacity. Otherwise, the machine’s actual disk capacity will be counted as a separate store for each node, thus inflating the computed capacity.

​
Live Bytes

The Live Bytes graph displays the amount of data that can be read by applications and CockroachDB. DB Console Replicas per Store Logical bytes reflect the approximate number of bytes stored in the database. This value may deviate from the number of physical bytes on disk, due to factors such as compression and write amplification.

​
File Descriptors

DB Console File Descriptors
  • In the node view, the graph shows the number of open file descriptors for that node, compared with the file descriptor limit.
  • In the cluster view, the graph shows the number of open file descriptors across all nodes, compared with the file descriptor limit.
If the Open count is almost equal to the Limit count, increase .
If you are running multiple nodes on a single machine (not recommended), the actual number of open file descriptors are considered open on each node. Thus the limit count value displayed on the DB Console is the actual value of open file descriptors multiplied by the number of nodes, compared with the file descriptor limit.
For Windows systems, you can ignore the File Descriptors graph because the concept of file descriptors is not applicable to Windows.

​
Other graphs

The Storage dashboard shows other time series graphs that are important for CockroachDB developers: For monitoring CockroachDB, it is sufficient to use the Capacity and File Descriptors graphs.

​
Summary and events

​
Summary panel

A Summary panel of key metrics is displayed to the right of the timeseries graphs. If you are testing your deployment locally with multiple CockroachDB nodes running on a single machine (this is ), you must explicitly per node in order to display the correct capacity. Otherwise, the machine’s actual disk capacity will be counted as a separate store for each node, thus inflating the computed capacity.

​
Events panel

Underneath the Summary panel, the Events panel lists the 5 most recent events logged for all nodes across the cluster. To list all events, click View all events. DB Console Events The following types of events are listed:
  • Database created
  • Database dropped
  • Table created
  • Table dropped
  • Table altered
  • Index created
  • Index dropped
  • View created
  • View dropped
  • Schema change reversed
  • Schema change finished
  • Node joined
  • Node decommissioned
  • Node restarted
  • Cluster setting changed

​
See also