> ## Documentation Index
> Fetch the complete documentation index at: https://cockroachlabs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Physical Cluster Replication Dashboard

export const InternalLink = ({version, path = "", children, ...props}) => {
  let detectedVersion = version || "stable";
  if (typeof window !== 'undefined' && !version) {
    const match = window.location.pathname.match(/\/docs\/([^/]+)/);
    if (match) {
      detectedVersion = match[1];
    }
  }
  const normalizedPath = path.startsWith("/") ? path.slice(1) : path;
  return <a href={`/docs/${detectedVersion}/${normalizedPath}`} {...props}>
      {children}
    </a>;
};

The **Physical Cluster Replication** dashboard in the DB Console lets you monitor the <InternalLink path="physical-cluster-replication-overview">physical cluster replication</InternalLink> streams between a primary and standby cluster.

To view this dashboard, <InternalLink path="ui-overview#db-console-access">access the DB Console</InternalLink> for your standby cluster, click **Metrics** on the left-hand navigation bar, and select **Physical Cluster Replication** from the **Dashboard** dropdown.

<Note>
  The **Physical Cluster Replication** dashboard is distinct from the <InternalLink path="ui-replication-dashboard">**Replication** dashboard</InternalLink>, which tracks metrics related to how data is replicated across the cluster, e.g., range status, replicas per store, etc.
</Note>

## 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 <InternalLink path="ui-overview#sql-activity">SQL Activity</InternalLink> pages. However, if you select 10 or 30 minutes, the interval defaults to 1 hour in SQL Activity pages.

Hovering your mouse pointer over the graph title will display a tooltip with a description and the <InternalLink path="essential-metrics-self-hosted ">metrics</InternalLink> used to create the graph.

When hovering on graphs, crosshair lines will appear at your mouse pointer. The series' values corresponding to the given time in the cross hairs are displayed in the legend under the graph. Hovering the mouse pointer on a given series displays the corresponding value near the mouse pointer and highlights the series line (graying out other series lines). Click anywhere within the graph to freeze the values in place. Click anywhere within the graph again to cause the values to change with your mouse movements once more.

In the legend, click on an individual series to isolate it on the graph. The other series will be hidden, while the hover will still work. Click the individual series again to make the other series visible. If there are many series, a scrollbar may appear on the right of the legend. This is to limit the size of the legend so that it does not get endlessly large, particularly on clusters with many nodes.

The **Physical Cluster Replication** dashboard displays the following time-series graphs:

## Logical bytes

<img src="https://mintcdn.com/cockroachlabs/4XH8VTm0CIsHBiqJ/images/v26.2/ui-logical-bytes.png?fit=max&auto=format&n=4XH8VTm0CIsHBiqJ&q=85&s=ea1117350914c5a85befdeb72e747350" alt="DB Console Logical Bytes graph showing results over the past hour" width="1926" height="756" data-path="images/v26.2/ui-logical-bytes.png" />

The **Logical Bytes** graph displays the throughput of the replicated bytes. The graph displays the rate at which the logical bytes (sum of keys + values) are ingested by all replication jobs.

Hovering over the graph displays:

* The date and time.
* The number of logical bytes replicated.

<Note>
  When you <InternalLink path="set-up-physical-cluster-replication#step-4-start-replication">start a replication stream</InternalLink>, the **Logical Bytes** graph will record a spike of throughput as the initial scan completes.
</Note>

## Replication lag

<img src="https://mintcdn.com/cockroachlabs/4XH8VTm0CIsHBiqJ/images/v26.2/ui-replication-lag.png?fit=max&auto=format&n=4XH8VTm0CIsHBiqJ&q=85&s=e04f341219961e03ee58f53ff47431dd" alt="DB Console Replication Lag graph showing results over the past hour" width="1440" height="556" data-path="images/v26.2/ui-replication-lag.png" />

The **Replication Lag** graph displays the <InternalLink path="physical-cluster-replication-technical-overview">replication lag</InternalLink> between the primary and standby cluster. This is the time between the most up-to-date replicated time and the actual time.

Hovering over the graph displays:

* The specific date and time of the replication lag.
* The reported replication lag time.

## 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](node-shutdown.html?filters=decommission) are not included in this count.                              |
| Capacity Used      | The storage capacity used as a percentage of <InternalLink path="ui-cluster-overview-page#capacity-metrics">usable capacity</InternalLink> 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.                                                                                                                                |

If you are testing your deployment locally with multiple CockroachDB nodes running on a single machine (this is <InternalLink path="recommended-production-settings#topology">not recommended in production</InternalLink>), you must explicitly <InternalLink path="cockroach-start#store">set the store size</InternalLink> 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](#summary-panel) 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**.

<img src="https://mintcdn.com/cockroachlabs/4XH8VTm0CIsHBiqJ/images/v26.2/ui_events.png?fit=max&auto=format&n=4XH8VTm0CIsHBiqJ&q=85&s=7fb6a16474396ffa6cebef3aceff5f49" alt="DB Console Events" width="668" height="1036" data-path="images/v26.2/ui_events.png" />

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

* <InternalLink path="physical-cluster-replication-overview">Physical Cluster Replication Overview</InternalLink>
* <InternalLink path="physical-cluster-replication-monitoring">Physical Cluster Replication Monitoring</InternalLink>
* <InternalLink path="troubleshooting-overview">Troubleshooting Overview</InternalLink>
* <InternalLink path="support-resources">Support Resources</InternalLink>
