📖
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
  1. Dashboard Installation
  2. Prometheus Jobs & Targets

Ethereum Metrics Exporter Targets

Customize the default Ethereum Metrics Exporter target

Previousjson_exporter TargetNextThird-Party Targets

Last updated 2 years ago

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.

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 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.

    - targets: ['192.168.2.6:9095']
      labels:
        network: 'Mainnet'
        host: 'nuc'
        service: 'Ethereum Metrics - Lodestar/Erigon'
        group: 'Mainnet Lodestar/Erigon'
        client: 'Ethereum Metrics Exporter'

Reminder: We are running Ethereum Metrics Exporter on a custom port (9095). The default port is 9090.

About Stake Local Labels