Authorized CockroachDB Advanced cluster users can visit the DB Console at a URL provisioned for the cluster.Refer to:
Authentication
The DB Console supports username/password login and single sign-on (SSO) for Advanced and clusters. The DB Console login page can also be used to provision authentication tokens for SQL client access. Refer to:- Single Sign-on (SSO) for DB Console
- [Cluster Single Sign-on (SSO) using JSON web tokens (JWTs)]
DB Console areas
Overview
The Overview page provides a cluster overview and node list and map.- has essential metrics about the cluster and nodes, including liveness status, replication status, uptime, and hardware usage.
- has a list of cluster metrics at the locality and node levels.
- displays a geographical configuration of your cluster and metrics at the locality and node levels, visualized on a map.
Metrics
The Metrics page provides dashboards for all types of CockroachDB metrics.- has metrics about SQL performance, replication, and storage.
- has metrics about CPU usage, disk throughput, network traffic, storage capacity, and memory.
- has metrics about node count, CPU time, and memory usage.
- has metrics about SQL connections, byte traffic, queries, transactions, and service latency.
- has metrics about storage capacity and file descriptors.
- has metrics about how data is replicated across the cluster, e.g., range status, replicas per store, and replica quiescence.
- has metrics about distribution tasks across the cluster, including RPCs, transactions, and node heartbeats.
- has metrics about the health and performance of various queueing systems in CockroachDB, including the garbage collection and Raft log queues.
- has metrics about important cluster tasks that take longer than expected to complete, including Raft proposals and lease acquisitions.
- has metrics about the created across your cluster.
- has metrics about the performance of the parts of your cluster relevant to the cluster’s .
- has metrics about the progress and performance of from your cluster.
Databases
The page shows details about the system and user databases in the cluster.SQL Activity
The SQL Activity page summarizes SQL activity in your cluster.- shows frequently executed and high-latency with the option to collect statement .
- shows details about transactions running on the cluster.
- shows details about open sessions in the cluster.
Insights
The page exposes problematic health signals and enables you to quickly find optimization opportunities to maximize database efficiency. The Insights page contains workload-level and schema-level insights.Network Latency
The page shows latencies and lost connections between all nodes in your cluster.Jobs
The page shows details of jobs running in the cluster.Advanced Debug
The page provides advanced monitoring and troubleshooting reports. These include details about data distribution, the state of specific queues, and slow query metrics. These details are largely intended for use by CockroachDB developers. To access the Advanced Debug page, the user must be a member of theadmin role or must have the VIEWDEBUG defined.
DB Console access
You can access the DB Console from every node athttp://<host:<http-port, or http://<host:8080 by default.
- If you included the flag when starting nodes, use the IP address or hostname and port specified by that flag.
- If you didn’t include the flag when starting nodes, use the IP address or hostname specified by the flag and port
8080. - If you are running a secure cluster, use
httpsinstead ofhttp.
Proxy DB Console
If your CockroachDB cluster is behind a load balancer, you may wish to proxy your DB Console connection to a different node in the cluster from the node you first connect to. This is useful in deployments where a third-party load balancer otherwise determines which CockroachDB node you connect to in DB Console, or where web management access is limited to a subset of CockroachDB instances in a cluster. You can accomplish this using one of these methods:- Once connected to DB Console, use the Web server dropdown menu from the page to select a different node to proxy to.
- Use the
remote_node_idparameter in your DB Console URL to proxy directly to a specific node. For example, usehttp://<host:<http-port/?remote_node_id=2to proxy directly to node2.
DB Console security considerations
Access to DB Console is a function of cluster security and the privileges of the accessing user.Cluster security
On insecure clusters, all areas of the DB Console are accessible to all users. On secure clusters, for each user who should have access to the DB Console, you must and optionally the user or membership to the .Privilege-based security
All users have access to data over which they have privileges (e.g., and ), and data that does not require privileges (e.g., , ). The following areas display information from privileged HTTP endpoints that require the user to have the or the specified .| DB Console area | System-level privilege | Privileged information |
|---|---|---|
| or | Stored table data | |
| or | SQL statements | |
| or | Transactions | |
| or | Sessions | |
| or | Insights | |
| Ranges | ||
| Jobs | ||
| Debugging and profiling endpoints | ||
| Ranges | ||
| Ranges | ||
| or | Cluster Settings |
DB Console timezone configuration
You can view timestamps in the DB Console in your preferred timezone using theui.display_timezone . Currently supported timezones are Coordinated Universal Time (etc/utc, the default) and America/New_York (america/new_york):
DB Console troubleshooting
The DB Console stores temporary data in a time-series database in order to generate the various metrics graphs. If your cluster is comprised of a large number of nodes where individual nodes have very limited memory available (e.g., under8 GiB), this underlying time-series database may not have enough memory available per-node to serve these requests quickly. If the DB Console experiences issues rendering these metrics graphs, consider increasing the value of the flag.