# Besu Dashboard Compatibility

## **Besu Dashboard Compatibility**

### Besu Overview Dashboard - Grafana 10273

Dashboard: <https://grafana.com/grafana/dashboards/10273-besu-overview/>

This Besu dashboard should work seamlessly with the Stake Local configuration if your prior Besu `job_name` was `besu`. `besu` is the default `job_name` for the [someresat](https://someresat.medium.com/guide-to-staking-on-ethereum-ubuntu-goerli-prysm-4a640794e8b5) and [Coin Cashew](https://www.coincashew.com/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/monitoring-your-validator-with-grafana-and-prometheus) guides to installing this Besu dashboard. If you used these guides, you may not need to make any changes.

If your prior Besu `job_name` was `besu-nodes`, this dashboard will continue to work, but historical data may show as a different data series under a different color. To avoid this problem, you may update the Nimbus `job_name` in the new `prometheus.yml` file to match your prior `job_name` value. `besu-nodes` is the default `job_name` for this [Consensys ](https://consensys.net/blog/developers/setting-up-monitoring-for-hyperledger-besu-in-aws/)guide.

**Optional**

Edit the `/etc/prometheus/prometheus.yml` file.

```bash
sudo vi /etc/prometheus/prometheus.yml
```

Find the line containing `- job_name: besu`.

Change that line to `- job_name: <PREVIOUS BESU job_name>`.

Replace `<PREVIOUS BESU JOB NAME>` with the `job_name` value for Besu in your previous `prometheus.yml` file. If you used the Consensys guide to setting up your original dashboard, this value may be `besu-nodes`.

Save the file and exit the editor.