📖
Stake Local Dashboard
  • Stake Local Dashboard
    • Library Sections
  • Dashboard Installation
    • Installation Overview
    • Install Supporting Software
      • Install Prerequisites
      • Install Prometheus
      • Install Grafana
      • Install node_exporter
      • Install json_exporter
      • Install Ethereum Metrics Exporter
    • Configure Ethereum Clients
    • Configure Supporting Software
      • Configure json_exporter
      • Configure Prometheus Rules
      • Configure Ethereum Metrics Exporter
    • Prometheus Jobs & Targets
      • Prometheus Jobs
      • About Stake Local Labels
      • Base Targets Installation
      • Consensus Client Targets
      • Execution Client Targets
      • Validator Client Targets
      • node_exporter Target
      • json_exporter Target
      • Ethereum Metrics Exporter Targets
      • Third-Party Targets
      • Ethereum Address Targets
      • Validator Public Key Targets
      • Optional: Grafana Target
      • Optional: Prometheus Target
      • Clean Up Unused Targets
    • Optional: Alternative Dashboard Compatibility
      • Besu Dashboard Compatibility
      • Erigon Dashboard Compatibility
      • Geth Dashboard Compatibility
      • Lighthouse Dashboard Compatibility
      • Lodestar Dashboard Compatibility
      • Nethermind Dashboard Compatibility
      • Nimbus Dashboard Compatibility
      • Prysm Dashboard Compatibility
      • Teku Compatibility
    • Enable & Start/Restart Services
      • Checking Software Status
    • Install Dashboard
  • Additional Modifications
    • Additional Staking Groups
    • Change or Add Currency
Powered by GitBook
On this page
  • Lighthouse Dashboard Compatibility
  • Lighthouse Summary Dashboard
  • Yoldark34 ETH Staking Dashboard
  1. Dashboard Installation
  2. Optional: Alternative Dashboard Compatibility

Lighthouse Dashboard Compatibility

How to keep other Lighthouse dashboards running with the Stake Local Dashboard

PreviousGeth Dashboard CompatibilityNextLodestar Dashboard Compatibility

Last updated 2 years ago

Lighthouse Dashboard Compatibility

Lighthouse Summary Dashboard

Dashboard:

This Lighthouse dashboard should work seamlessly with the Stake Local configuration if your prior Lighthouse beacon chain job_name was lighthouse_beacon. and your prior Lighthouse validator job_name was lighthouse_validator.

If your prior Lighthouse beacon chain or validator job_name were any other value, this dashboard will continue to work, but historical data may show as a different data series under a different color if it is in the selected time range. To avoid this problem, you may update the Lighthouse beacon chain and validator job_name values in the new prometheus.yml file to match your prior job_name values. nodes and validators are the default job_name values from this Coin Cashew guide. lighthouse is the default job_name from this someresat guide. local-lighthouse is the default job_name from this SigmaPrime guide.

Optional

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

sudo vi /etc/prometheus/prometheus.yml

Find the line containing - job_name: lighthouse_beacon.

Change that line to - job_name: <PREVIOUS LIGHTHOUSE BEACON job_name>.

Replace <PREVIOUS LIGHTHOUSE BEACON JOB NAME> with the value for Besu in your previous prometheus.yml file. If you used the somersat guide to setting, this value may be lighthouse.

Save the file and exit the editor.

Yoldark34 ETH Staking Dashboard

Dashboard:

This Lighthouse dashboard is not compatible with the Stake Local configuration without some additional configuration.

To continue to use this Lighthouse dashboard, update the Nimbus job_name in the new prometheus.yml file to match your prior value. lighthouse is the default for this Coin Cashew guide to installing a Nimbus dashboard.

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

sudo vi /etc/prometheus/prometheus.yml

Find the line containing - job_name: lighthouse_beacon.

Change that line to - job_name: <PREVIOUS LIGHTHOUSE BEACON job_name>.

Replace <PREVIOUS LIGHTHOUSE BEACON JOB NAME> with the value for Lighthouse beacon chain in your previous prometheus.yml file. If you used the Coin Cashew guide to setting up your original dashboard, this value may be nodes.

Find the line containing - job_name: lighthouse_validator.

Change that line to - job_name: <PREVIOUS LIGHTHOUSE VALIDATOR job_name>.

Replace <PREVIOUS LIGHTHOUSE VALIDATOR JOB NAME> with the value for Lighthouse validator in your previous prometheus.yml file. If you used the Coin Cashew guide to setting up your original dashboard, this value may be validators.

The Coin Cashew guide to installing this dashboard recommends the Lighthouse beacon job_name of nodes and the Lighthouse validator job_name of validators. Some queries in this dashboard require the use of lighthouse and lighthouse_validator for those job_name values, respectively. Changing the job_name values to lighthouse and lighthouse_validator instead of your previous values will enable all queries in this dashboard to work, but historical data may appear under a separate color/legend from present data.

Save the file and exit the editor.

If the Lighthouse beacon chain or Lighthouse validator job names are changed from their Stake Local defaults, please complete the steps to update the job name variables during .

https://raw.githubusercontent.com/sigp/lighthouse-metrics/master/dashboards/Summary.json
https://raw.githubusercontent.com/Yoldark34/lighthouse-staking-dashboard/main/Yoldark_ETH_staking_dashboard.json
dashboard installation