Validator Public Key Targets

Add targets for Ethereum addresses to be monitored

Validator Public Key Targets

Prometheus collects individual validator balances and status information from consensus clients via json_exporter. Validators may be specified by public key or validator index.

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

sudo nano /etc/prometheus/files_sd/stakelocal/validators.yml

It should look like the following.

    - targets: [ ]
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: ''
        group: 'Default Group'
        instance: '127.0.0.1:3500'
        explorer: 'beaconcha.in'

Update the targets line to include a comma-delimited list of validator public keys or indices to be monitored in between the square brackets.

Example values:

• -targets: [ 1, 2, 3, 4, 5 ]

• -targets: [ 0x0000000000000000000000000000000000000000, 0x0000000000000000000000000000000000000000, 0x0000000000000000000000000000000000000000 ]

• -targets: [ 1, "2", '3', 0x0000000000000000000000000000000000000000, "0x0000000000000000000000000000000000000000", '0x0000000000000000000000000000000000000000']

If the consensus client being queried is not on the local host or uses a non-standard port, update those on the instance line.

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

The service label is optional. It only serves to identify the type of client being queried in Ethereum address requests, but the value itself is not presently used in the dashboard.

An example validators.yml file for the Goerli network could look like the following.

    - targets: [ 1, 2, 3 ]
      labels:
        network: 'Goerli'
        host: 'nuc'
        service: 'Prysm Beacon'
        group: 'Goerli Prysm/Geth'
        instance: '127.0.0.1:3500'
        explorer: 'goerli.beaconcha.in'

Save the file and exit the editor.