📖
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
  • Validator Client Targets
  • Validator Client Metrics Configuration
  1. Dashboard Installation
  2. Prometheus Jobs & Targets

Validator Client Targets

Customize the default validator client targets

PreviousExecution Client TargetsNextnode_exporter Target

Last updated 2 years ago

Validator Client Targets

Prometheus may also collect metrics data from validator clients that run as a separate process from the beacon chain client. Some validator clients produce more detailed validator status information than available from beacon chain clients.

Validator clients for Lighthouse, Lodestar, and Prysm have been tested with the dashboard.

If you would like to monitor more than one instance of the same client, please see the Additional Modifications section for details.

Validator Client Metrics Configuration

To configure the Prometheus target for client metrics, follow the instructions for your client below.

Edit the Lighthouse configuration file in the /etc/prometheus/files_sd/stakelocal/validator_metrics directory.

sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/lighthouse.yml

It should look like the following.

    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Lighthouse Validator'
        group: 'Default Group'

If this instance of Lighthouse is accessible at a different IP address or port, update those in the targets line.

Update the network, host, service, group and explorer labels, as needed. See for label definitions.

Save the file and exit the editor.

Edit the Lodestar configuration file in the /etc/prometheus/files_sd/stakelocal/validator_metrics directory.

sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/lodestar.yml

It should look like the following.

    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Lodestar Validator'
        group: 'Default Group'

If this instance of Lodestar is accessible at a different IP address or port, update those in the targets line.

Update the network, host, service, group and explorer labels, as needed. See for label definitions.

Save the file and exit the editor.

Edit the Prysm configuration file in the /etc/prometheus/files_sd/stakelocal/validator_metrics directory.

sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/prysm.yml

It should look like the following.

    - targets: ['127.0.0.1:8081']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Prysm Validator'
        group: 'Default Group'

If this instance of Prysm is accessible at a different IP address or port, update those in the targets line.

Save the file and exit the editor.

An example validator client metrics target file for the Goerli network could look like the following.

    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Goerli'
        host: 'stakemaster5000'
        service: 'Lodestar Validator - Goerli'
        group: 'Goerli Lodestar/Geth'

Update the network, host, service, group and explorer labels, as needed. See for label definitions.

About Stake Local Labels
About Stake Local Labels
About Stake Local Labels