Ethereum Metrics Exporter Targets
Customize the default Ethereum Metrics Exporter target
Ethereum Metrics Exporter Targets
For accessing Ethereum client APIs, Ethereum Metrics Exporter has an advantage over json_exporter. It can craft API queries that json_exporter cannot, and it maintains state over time, allowing it to subscribe to events, for example.
The dashboard was nearly complete before Ethereum Metrics Exporter was incorporated. There is overlap in the data provided by Ethereum Metrics Exporter and json_exporter, but both have been retained in the solution for now.
Edit the Ethereum Metrics Exporter configuration file in the /etc/prometheus/files_sd/stakelocal/other/
directory.
sudo nano /etc/prometheus/files_sd/stakelocal/other/eth-metrics.yml
It should look like the following.
- targets: ['127.0.0.1:9095']
labels:
network: 'Mainnet'
host: 'Default Host'
service: 'Ethereum Metrics Exporter'
group: 'Default Group'
client: 'Ethereum Metrics Exporter'
If the Ethereum Metrics Exporter instance being queried is not on the local host or uses a non-standard port, update those on the targets
line.
Update the network
, host
, service
, and group
labels, as needed. See About Stake Local Labels for label definitions.
Save the file and exit the editor.
An example target file could look like the following.
- targets: ['192.168.2.6:9095']
labels:
network: 'Mainnet'
host: 'nuc'
service: 'Ethereum Metrics - Lodestar/Erigon'
group: 'Mainnet Lodestar/Erigon'
client: 'Ethereum Metrics Exporter'
Last updated