# Configure Ethereum Metrics Exporter

## Configure Ethereum Metrics Exporter

Edit the `eth-metrics.yml` file.

```bash
sudo nano /etc/eth-metrics/eth-metrics.yml
```

Insert the following text into the `eth-metrics.yml` file.

```yaml
consensus:
  enabled: true
  url: "<CONSENSUS_CLIENT_URL>"
  name: "<CONSENSUS_CLIENT_NAME>"
execution:
  enabled: true
  url: "<EXECUTION_CLIENT_URL>"
  name: "<EXECUTION_CLIENT_NAME>"
  modules:
    - "eth"
    - "net"
    - "web3"
    - "txpool"
pair:
  enabled: true
```

Make the following customizations to the text inserted:

1. Replace `<CONSENSUS_CLIENT_URL>` with the URL to your consensus client API. It should look similar to `http://localhost:3500/`. You can replace `localhost` with the IP address of your consensus client, if it is not running on the local host. Use the correct port for your consensus client.

   \
   **Default Consensus Client API Ports**

   1. Lighthouse: 5052
   2. Lodestar: 9596
   3. Nimbus: 5052
   4. Prysm: 3500
   5. Teku: 5051
2. Replace `<CONSENSUS_CLIENT_NAME>` with one of the following execution client names: `Lighthouse Beacon`, `Lodestar Beacon`, `Nimbus`, `Prysm Beacon`, `Teku`.
3. Replace `<EXECUTION_CLIENT_URL>` with the URL to your execution client API. It should look similar to `http://localhost:8545`. You can replace `localhost` with the IP address of your execution client, if it is not running on the local host. All execution clients use the same port.
4. Replace `<EXECUTION_CLIENT_URL>` with one of the following execution client names: `Besu`, `Erigon`, `Geth`, `Nethermind`.

When you are done making changes, you final `eth-metrics.yml` file might look something like the following.

```yaml
consensus:
  enabled: true
  url: "http://127.0.0.1:3500/"
  name: "Prysm Beacon"
execution:
  enabled: true
  url: "http://127.0.0.1:8545/"
  name: "Geth"
  modules:
    - "eth"
    - "net"
    - "web3"
    - "txpool"
pair:
  enabled: true
```

Save the file and exit the editor.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stakelocal.io/dashboard-installation/configure-supporting-software/configure-ethereum-metrics-exporter.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.