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

# basectl monitor: interactive terminal dashboard

> Open live terminal dashboards for Base block production, node sync, Flashblocks, data availability, conductor clusters, and network upgrades with basectl monitor.

`basectl monitor` opens an interactive dashboard in your terminal. Run it with no subcommand to open the Home view. The badge in the top-right corner shows which execution-layer (EL) and consensus-layer (CL) endpoints are active.

Press `e` from any view (except text-input views) to switch the EL endpoint between your configured local node (`rpc`) and the hosted public endpoint (`public_rpc`). The CL endpoint stays the same. When you switch, the dashboard reconnects its live data to the endpoint you picked.

## Views

Open a specific view by adding its name (or short alias) after `monitor`:

| Command                  | Alias | Description                                                  |
| ------------------------ | ----- | ------------------------------------------------------------ |
| `monitor`                |       | Home view.                                                   |
| `monitor conductor`      | `co`  | Conductor cluster status.                                    |
| `monitor da`             | `d`   | Data-availability (DA) backlog.                              |
| `monitor flashblocks`    | `f`   | Live Flashblocks.                                            |
| `monitor command-center` | `cc`  | Combined view of several panels.                             |
| `monitor upgrades`       | `u`   | Countdown to the next network upgrade, plus upgrade history. |
| `monitor config`         | `c`   | The active network configuration.                            |

## Pods view

`basectl monitor pods` shows the status of your Kubernetes pods, grouped as defined in a local config file. Keep environment-specific values (names, namespaces, contexts, and URLs) in your own local config; the public tool only defines the general structure.

```yaml network-config.yaml theme={null}
pods:
  refresh_interval_ms: 1000
  groups:
    - alias: example
      label: Example
      context: example-context
      namespace: example-namespace
```

## Examples

```bash Open the dashboard theme={null}
# Open the Home view on mainnet
basectl monitor

# Open the dashboard on a local devnet
basectl -c devnet monitor

# Open the conductor cluster view directly
basectl monitor conductor
```

## Related

* [basectl overview](/base-chain/node-operators/basectl/overview)
* [Inspect blocks and sync](/base-chain/node-operators/basectl/block-and-sync)
* [Operate sequencer clusters](/base-chain/node-operators/basectl/conductor-and-sequencer)