> 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/optional-alternative-dashboard-compatibility/teku-compatibility.md).

# Teku Compatibility

## Teku

### Teku Dashboard - Grafana 13457

Dashboard: <https://grafana.com/grafana/dashboards/13457-teku/>

This Teku dashboard should work seamlessly with the Stake Local configuration if your prior Teku `job_name` was `teku`.

If your prior Teku `job_name` was anything else, this dashboard will continue to work, but historical data may show as a different data series under a separate color/legend. To avoid this problem, you may update the Teku `job_name` in the new `prometheus.yml` file to match your prior `job_name` value. `nodes` is the default `job_name` for the Coin Cashew and someresat guides.

**Optional**

Edit the `/etc/prometheus/prometheus.yml` file.

```bash
sudo vi /etc/prometheus/prometheus.yml
```

Find the line containing `- job_name: teku`.

Change that line to `- job_name: <PREVIOUS TEKU job_name>`.

Replace `<PREVIOUS TEKU JOB NAME>` with the `job_name` value for Teku in your previous `prometheus.yml` file. If you used the Coin Cashew or someresat guides to setting up this dashboard, this value may be `nodes`.

Save the file and exit the editor.


---

# 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:

```
GET https://docs.stakelocal.io/dashboard-installation/optional-alternative-dashboard-compatibility/teku-compatibility.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.