> For the complete documentation index, see [llms.txt](https://docs.stakelocal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakelocal.io/dashboard-installation/prometheus-jobs-and-targets/validator-client-targets.md).

# Validator Client Targets

## Validator Client Targets

Prometheus may also collect metrics data from validator clients that run as a separate process from the beacon chain client. Some validator clients produce more detailed validator status information than available from beacon chain clients.

{% hint style="warning" %}
Validator clients for Lighthouse, Lodestar, and Prysm have been tested with the dashboard.
{% endhint %}

{% hint style="info" %}
If you would like to monitor more than one instance of the same client, please see the Additional Modifications section for details.
{% endhint %}

### Validator Client Metrics Configuration

To configure the Prometheus target for client metrics, follow the instructions for your client below.

{% tabs %}
{% tab title="Lighthouse" %}
Edit the Lighthouse configuration file in the `/etc/prometheus/files_sd/stakelocal/validator_metrics` directory.

```bash
sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/lighthouse.yml
```

It should look like the following.

```yaml
    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Lighthouse Validator'
        group: 'Default Group'
```

If this instance of Lighthouse is accessible at a different IP address or port, update those in the `targets` line.

Update the `network`, `host`, `service`, `group` and `explorer` labels, as needed. See [About Stake Local Labels](/dashboard-installation/prometheus-jobs-and-targets/about-stake-local-labels.md) for label definitions.

Save the file and exit the editor.
{% endtab %}

{% tab title="Lodestar" %}
Edit the Lodestar configuration file in the `/etc/prometheus/files_sd/stakelocal/validator_metrics` directory.

```bash
sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/lodestar.yml
```

It should look like the following.

```yaml
    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Lodestar Validator'
        group: 'Default Group'
```

If this instance of Lodestar is accessible at a different IP address or port, update those in the `targets` line.

Update the `network`, `host`, `service`, `group` and `explorer` labels, as needed. See [About Stake Local Labels](/dashboard-installation/prometheus-jobs-and-targets/about-stake-local-labels.md) for label definitions.

Save the file and exit the editor.
{% endtab %}

{% tab title="Prysm" %}
Edit the Prysm configuration file in the `/etc/prometheus/files_sd/stakelocal/validator_metrics` directory.

```bash
sudo nano /etc/prometheus/files_sd/stakelocal/validator_metrics/prysm.yml
```

It should look like the following.

```yaml
    - targets: ['127.0.0.1:8081']
      labels:
        network: 'Mainnet'
        host: 'Default Host'
        service: 'Prysm Validator'
        group: 'Default Group'
```

If this instance of Prysm is accessible at a different IP address or port, update those in the `targets` line.

Update the `network`, `host`, `service`, `group` and `explorer` labels, as needed. See [About Stake Local Labels](/dashboard-installation/prometheus-jobs-and-targets/about-stake-local-labels.md) for label definitions.

Save the file and exit the editor.
{% endtab %}
{% endtabs %}

An example validator client metrics target file for the Goerli network could look like the following.

```
    - targets: ['127.0.0.1:5064']
      labels:
        network: 'Goerli'
        host: 'stakemaster5000'
        service: 'Lodestar Validator - Goerli'
        group: 'Goerli Lodestar/Geth'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.stakelocal.io/dashboard-installation/prometheus-jobs-and-targets/validator-client-targets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.