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.
The redundant API calls may be removed in the future. For now, having both sources of data provides some flexibility to not install Ethereum Metrics Exporter and still have much of the same functionality. A small number of dashboard panels will stop working entirely if Ethereum Metrics Exporter is not installed.
Edit the Ethereum Metrics Exporter configuration file in the /etc/prometheus/files_sd/stakelocal/other/
directory.
It should look like the following.
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.
Each instance of Ethereum Metrics Exporter can only serve a single pair of consensus and execution clients. Repeat this configuration for each instance of Ethereum Metrics Exporter to be monitored.
Save the file and exit the editor.
An example target file could look like the following.
Reminder: We are running Ethereum Metrics Exporter on a custom port (9095). The default port is 9090.
Last updated