> 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/base-targets-installation.md).

# Base Targets Installation

Download and unpack the archive of default target configuration files. This will install configuration files for all supported clients. We can [clean up the unused target](/dashboard-installation/prometheus-jobs-and-targets/clean-up-unused-targets.md) files later.

```bash
cd ~/git/stakelocal-dashboard
sudo tar xzvf stakelocal_prometheus_targets.tgz -C /etc/prometheus/files_sd
```

<figure><img src="/files/UO8N0F8D3O3F71MknoJ6" alt=""><figcaption><p>Results of <code>tar</code> command</p></figcaption></figure>

Clean up the archive file now that we have unpacked it.

```bash
rm stakelocal_prometheus_targets.tgz
```

Most of the targets unpacked will have default IP addresses, ports, and label values suitable to get the dashboard up and running quickly without modification.

Specifically, the default target files assume the following.

* All clients and supporting software are accessible at 127.0.0.1 from any other client.
* All clients and supporting software are using the ports defined in this guide, nearly all of which are the client default ports.

And the default labels are assigned as follows.

* Where used, the `network` label is set to "Mainnet".
* Where used, the `host` label is set to "Default Host".
* Where used, the `group` label is set to "Default Group".
* Where used, the `explorer` label is set to "beaconcha.in" or "etherscan.io".

If these assumptions and defaults are acceptable, you can jump ahead to [Ethereum Address Targets](/dashboard-installation/prometheus-jobs-and-targets/ethereum-address-targets.md) and continue from there. Changes can always be made later, and Prometheus will automatically reload these configuration files without running any restart/reload commands.

{% hint style="info" %}
You may want to review and update the label values now. Label values that are changed in the future may cause historical data to appear as a different data series with separate colors/legends for as long as the historical data is within view.
{% endhint %}

If your clients or supporting software are not accessible at `127.0.0.1` or are running on non-standard ports, you must continue to the next sections.

The following sections will guide you through a review of the Prometheus targets we just unpacked. Making changes as necessary to IP addresses, ports, or labels.


---

# 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/base-targets-installation.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.