> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/deploy/installation/production-setup/install-monitoring-stack/2.-deploy.md).

# 2. Deploy

## **Overview**

This guide walks you through deploying the monitoring stack (Grafana, Loki, Prometheus, Alertmanager) using **Helmfile**.

## Steps

### Step 1: Navigate to the Monitoring Directory

Move to the directory that contains the monitoring Helmfile.

```
cd deploy-as-code/helm/charts/monitoring
```

This directory contains the `monitoring-helmfile.yaml`, that controls the deployment.

### Step 2: Preview the Kubernetes Manifests (Dry Run)

Verify the environment configuration. Open `monitoring-helmfile.yaml` and confirm the environment name.

```
helmfile -f monitoring-helmfile.yaml -e <environment> template
```

**Why this matters**

* Validates Helm values and templates
* Helps catch configuration issues early
* Shows exactly what Kubernetes resources will be created

### Step 3: Review the Differences (Diff)

Compare the currently deployed resources with the desired state defined in Helmfile.

* ```
  helmfile -f monitoring-helmfile.yaml -e <environment> diff
  ```

### Step 4: Apply the Changes to the Cluster

Once the diff looks correct, apply the changes to the Kubernetes cluster.

```
helmfile -f monitoring-helmfile.yaml -e <environment> apply
```

{% hint style="info" %}
In the above commands, use the **environment** as set in **monitoring-helmfile.yaml**; in this case, it’ll be “demo“. Example - helmfile -f monitoring-helmfile.yaml -e demo apply
{% endhint %}

This will:

* Install the monitoring stack if not already present
* Upgrade existing components if the configuration has changed


---

# 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.digit.org/health/deploy/installation/production-setup/install-monitoring-stack/2.-deploy.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.