> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/pharos-node-monitoring.md).

# Pharos Node Monitoring

We recommend deploying Prometheus, Pushgateway, and Grafana to monitor Pharos Node metrics.

## Deploy Prometheus and pushgateway

If you have already deployed a Prometheus monitoring and alerting system, you can skip this step:

1. **Create the Prometheus namespace:**

<pre class="language-sh"><code class="lang-sh"><strong>kubectl create namespace prometheus
</strong></code></pre>

2. **Add the** <mark style="color:green;">`prometheus-community`</mark> **chart repository:**

```sh
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
```

3. **Deploy Prometheus:**

```sh
helm upgrade -i prometheus prometheus-community/prometheus \
--namespace prometheus \
--set alertmanager.persistence.storageClass="gp2" \
--set server.persistentVolume.storageClass="gp2"
```

4. **Verify that all pods in the** prometheus **namespace are in the** <mark style="color:green;">`READY`</mark> **state:**

```sh
kubectl get pods -n prometheus
```

5. **Get the Pushgateway Service IP/Domain:**

```sh
kubectl -n prometheus-agent-namespace get svc
```

You should see the <mark style="color:green;">`prometheus-pushgateway`</mark> Service. Save the <mark style="color:green;">`IP address`</mark> of the Pushgateway Service.

## Modify the metrics push configuration file

For detailed instructions on configuring the metrics push in your `pharos.conf`, see [Node Monitoring Setup](/node-and-validator-guide/node-monitoring-setup.md).


---

# 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.pharos.xyz/pharos-node-monitoring.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.