TTL Dashboard

On this page Carat arrow pointing down
Warning:
GA releases for CockroachDB v23.1 are no longer supported. Cockroach Labs will stop providing LTS Assistance Support for v23.1 LTS releases on November 13, 2025. Prior to that date, upgrade to a more recent version to continue receiving support. For more details, refer to the Release Support Policy.

The TTL dashboard lets you monitor the progress and performance of batch deleting expired data using Row-Level TTL from your cluster.

To view this dashboard, access the DB Console, click Metrics in the left-hand navigation, and select Dashboard > TTL.

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 SQL Activity 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 TTL dashboard displays the following time series graphs:

Processing Rate

You can monitor the Processing Rate graph to see how many rows per second are being processed by TTL jobs.

TTL processing rate graph

Metric Description
rows selected The number of rows selected for deletion by the TTL job.
rows deleted The number of rows deleted by the TTL job.

Estimated Rows

Monitor the Estimated Rows graph to see approximately how many rows are on the TTL table.

TTL estimated rows graph

Metric Description
approximate number of rows The number of rows in all tables with TTL settings.
approximate number of expired rows The number of expired rows across all tables with TTL settings.

Job Latency

Monitor the Job Latency graph to see the latency of scanning and deleting within your cluster's TTL jobs.

TTL job latency graph

Ranges in Progress

Monitor the Ranges in Progress graph to see the number of ranges currently being processed by TTL jobs.

TTL ranges in progress graph

Metric Description
number of ranges being processed How many ranges are currently being processed by TTL jobs.

Summary and events

Summary panel

A Summary panel of key metrics is displayed to the right of the timeseries graphs.

Metric Description
Total Nodes The total number of nodes in the cluster. Decommissioned nodes are not included in this count.
Capacity Used The storage capacity used as a percentage of usable capacity allocated across all nodes.
Unavailable Ranges The number of unavailable ranges in the cluster. A non-zero number indicates an unstable cluster.
Queries per second The total number of SELECT, UPDATE, INSERT, and DELETE queries executed per second across the cluster.
P99 Latency The 99th percentile of service latency.
Note:

If you are testing your deployment locally with multiple CockroachDB nodes running on a single machine (this is not recommended in production), you must explicitly set the store size 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


Yes No
On this page

Yes No