📖
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
  • Lodestar Dashboard Compatibility
  • ChainSafe Lodestar Summary Dashboard
  1. Dashboard Installation
  2. Optional: Alternative Dashboard Compatibility

Lodestar Dashboard Compatibility

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

PreviousLighthouse Dashboard CompatibilityNextNethermind Dashboard Compatibility

Last updated 2 years ago

Lodestar Dashboard Compatibility

ChainSafe Lodestar Summary Dashboard

Dashboard:

The Lodestar dashboard listed above has a hard-coded job_name in many queries. To continue to use this dashboard, the Lodestar job_name in the new configuration file must be updated to match the hard-coded value.

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

sudo vi /etc/prometheus/prometheus.yml

Find the line containing - job_name: lodestar_beacon.

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

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

Find the line containing - job_name: lodestar_validator.

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

Replace <PREVIOUS LODESTAR VALIDATOR job_name> with the value for the Lodestar beacon in your previous prometheus.yml file. You may not have this job in your prior prometheus.yml configuration file.

The Coin Cashew and someresat guides may recommend default job_name values that are incompatible with some portions of the alternative Lodestar dashboard. You may continue to use the prior values recommended by these guides for a consistent user experience. However, using the values beacon and validator in place of your prior values may provide more complete functionality for the original dashboard. This will cause the color change effect for historical data on the alternative Lodestar dashboard, but full functionality should be returned to the dashboard.

Replace <PREVIOUS LODESTAR JOB NAME> with the 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.

https://raw.githubusercontent.com/ChainSafe/lodestar/.../lodestar_summary.json