# Sending Metrics

Once you have uploaded your keys and set up your own monitoring, you should start sending metrics to Obol so they can provide better tech support.

Go to the Obol package on your Dappnode and click on Config. On the bottom you will see this: 

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FuCTXLt6sT2XleTqLcErg%2FScreenshot%202024-12-16%20at%2017.41.25.png?alt=media&#x26;token=16364b4e-9b87-4af8-a1ab-2b7b3fcea53b" alt=""><figcaption></figcaption></figure>

Are you running multiple Charon clients, i.e. participating in multiple clusters? If not, set "Charons to monitor" to "1". If yes, add all clusters that you want to monitor.

Set the prometheus monitoring url to:

```
https://vm.monitoring.gcp.obol.tech/write
```

Set the prometheus monitoring credentials to the value you will receive from the Etherfi or Obol team.

```
obolpF5...
```


---

# 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://etherfi.gitbook.io/etherfi/solo-stakers/operation-solo-staker/obol-dvt-explained/dappnode-setup/obol-dvt-package/sending-metrics.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.