--- title: "Deploy Loki meta-monitoring with chart version 3 | Grafana Loki documentation" description: "Describes how to deploy Meta Monitoring for Loki using version 3.8.x of the Kubernetes Monitoring Helm chart." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Deploy Loki meta-monitoring with chart version 3 The primary method for collecting and monitoring a Loki cluster is to use the [Kubernetes Monitoring Helm](https://github.com/grafana/k8s-monitoring-helm/) chart. This chart provides a comprehensive monitoring solution for Kubernetes clusters and includes direct integrations for monitoring the full LGTM (Loki, Grafana, Tempo, and Mimir) stack. This procedure will walk you through deploying version 3.8.x of the Kubernetes Monitoring Helm chart to monitor your Loki cluster. > Note > > This page covers chart version 3.8.x, which is a maintained stable release line. If you do not already have a reason to stay on chart 3.8.x, use [Deploy Loki meta-monitoring](/docs/loki/latest/operations/meta-monitoring/deploy/) instead, which covers the current chart 4.x line. For help moving from chart 3.x to 4.x, refer to the [Kubernetes Monitoring Helm chart migration guide](/docs/grafana-cloud/monitor-infrastructure/kubernetes-monitoring/configuration/helm-chart-config/helm-chart/migrate-helm-chart/). > Note > > We recommend running a production cluster of Loki in distributed mode using Kubernetes. This procedure assumes you have a running Kubernetes cluster and a running Loki deployment. There are other methods for deploying Loki, such as using Docker or VM installations. meta-monitoring is still possible when using these deployment methods but not covered in this procedure. ## Prerequisites - [kubectl](https://kubernetes.io/docs/reference/kubectl/) - Helm 3 or above. See [Installing Helm](https://helm.sh/docs/intro/install/). - A running Kubernetes cluster with a running Loki deployment. - A Grafana Cloud account or a separate LGTM stack for monitoring. ## Preparing your environment Before deploying the Kubernetes Monitoring Helm chart, you need to set up several components in your environment. 1. Add the Grafana Helm repository: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm repo add grafana https://grafana.github.io/helm-charts ``` 2. Update your Helm repositories: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm repo update ``` 3. Create a namespace for the monitoring stack: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash kubectl create namespace meta ``` ### Authentication The Kubernetes Monitoring Helm chart requires a Grafana Cloud account or a separate LGTM stack for monitoring. You will need to provide the necessary credentials to the Helm chart to authenticate with your Grafana Cloud account or LGTM stack. In this procedure, we will use Grafana Cloud as an example. 1. Create a new Cloud Access Policy in Grafana Cloud. 1. Sign into [Grafana Cloud](/auth/sign-in/). 2. In the main menu, select **Security > Access Policies**. 3. Click **Create access policy**. 4. Give the policy a **Name** and select the following permissions: - Metrics: Write - Logs: Write 5. Click **Create**. 6. Click **Add Token**. Give the token a name and click **Create**. Save the token for later use. 2. Collect `url` and `username` for Prometheus and Loki. 1. Navigate to the Grafana Cloud Portal **Overview** page. 2. Click the **Details** button for your Prometheus instance. 1. From the **Sending metrics using Grafana Alloy** section, collect the instance **username** and **url**. 2. Navigate back to the **Overview** page. 3. Click the **Details** button for your Loki instance. 1. From the **Sending Logs to Grafana Cloud using Grafana Alloy** section, collect the instance **username** and **url**. 2. Navigate back to the **Overview** page. 3. Create the Kubernetes Secrets with the collected credentials from Grafana Cloud. Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash kubectl create secret generic metrics -n meta \ --from-literal=username= \ --from-literal=password= kubectl create secret generic logs -n meta \ --from-literal=username= \ --from-literal=password= ``` Note that the Kubernetes Monitoring Helm supports many different authentication methods based upon your requirements including: - Bearer Tokens - OAuth2 - SigV4 - External Secrets For further information on how to configure these methods, see the [Kubernetes Monitoring Helm examples](https://github.com/grafana/k8s-monitoring-helm/tree/main/charts/k8s-monitoring/docs/examples/auth). ## Deploy the Kubernetes Monitoring Helm chart Now that you have prepared your environment and collected the necessary credentials, you can deploy the Kubernetes Monitoring Helm chart to monitor your Loki cluster. To do this we need to copy a `values.yaml` file to our local machine and modify it to include the necessary configuration. 1. Download the `values-chart-v3.yaml` file from the Kubernetes Monitoring Helm chart repository: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash curl -O https://raw.githubusercontent.com/grafana/loki/main/production/helm/meta-monitoring/values-chart-v3.yaml ``` 2. Open the `values-chart-v3.yaml` file in a text editor of your choosing and add the Prometheus and Loki endpoints. YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml destinations: - name: prometheus type: prometheus url: https:///api/prom/push auth: type: basic usernameKey: username passwordKey: password secret: create: false name: metrics namespace: meta - name: loki type: loki url: https:///loki/api/v1/push auth: type: basic usernameKey: username passwordKey: password secret: create: false name: logs namespace: meta ``` 3. (Optional) Update the cluster name to a human-readable name to identify your cluster in Grafana Cloud. YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml # Global Label to be added to all telemetry data. Should reflect a recognizable name for the cluster. cluster: name: loki-meta-monitoring-cluster ``` 4. The default values file assumes that you have deployed Loki in the `loki` namespace and will deploy the Kubernetes monitoring stack in the `meta` namespace. If you have deployed Loki in a different namespace, or the monitoring stack in a namespace other than `meta`, you will need to update several keys in `values-chart-v3.yaml`. There is no single `namespaces` key; namespace scoping is set independently for each feature: Expand table | Key | Format | Purpose | |-----------------------------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------| | `integrations.loki.instances[0].namespaces` | list | Namespace(s) to discover Loki instances in. | | `integrations.alloy.instances[0].namespaces` | list | Namespace(s) to discover the monitoring stack’s own Alloy collectors in. | | `clusterEvents.namespaces` | list | Namespace(s) to capture Kubernetes events from. | | `clusterMetrics.cadvisor.metricsTuning.includeNamespaces` | list | Namespace(s) to keep cadvisor metrics for. This is a metric filter, not a discovery scope. | | `clusterMetrics.kube-state-metrics.namespaces` | list, or comma-separated string | Namespace(s) to collect Kubernetes resource state from. | | `podLogs.namespaces` | list | Namespace(s) to collect pod logs from. | For example, to add a namespace to the Loki discovery scope: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml integrations: loki: instances: - name: loki namespaces: - loki ``` Each of these keys defaults to an empty list, which means “collect from all namespaces”. Removing a key restores that default for that feature only; it does not affect the other keys in this table. Also note that `destinations[].secret.namespace` (used for both the `metrics` and `logs` destinations) must match the namespace where you created the `metrics` and `logs` secrets, which is `meta` by default. Update it if you installed the monitoring stack into a different namespace. 5. Deploy the Kubernetes Monitoring Helm chart using the modified `values-chart-v3.yaml` file, pinning the chart to the 3.x line: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm install meta-loki grafana/k8s-monitoring \ --namespace meta \ --version "^3" \ -f values-chart-v3.yaml ``` 6. Verify that the Kubernetes Monitoring Helm chart has been deployed successfully: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash kubectl get pods -n meta ``` You should see a list of pods running in the `meta` namespace. console ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```console NAME READY STATUS RESTARTS ... meta-loki-alloy-singleton-6d7f8d8b86-sg4wx 2/2 Running 0 ... meta-loki-kube-state-metrics-64bdcfcbd-5snqz 1/1 Running 0 ... meta-loki-node-exporter-855l5 1/1 Running 0 ... meta-loki-node-exporter-b976b 1/1 Running 0 ... meta-loki-node-exporter-vsm4s 1/1 Running 0 ... ``` ## Next Steps You have successfully deployed the Kubernetes Monitoring Helm chart to monitor your Loki cluster. You can now move onto the next step of deploying the Loki mixin to visualize the metrics and logs from your Loki cluster. For more information, see [Install the Loki Mixin](/docs/loki/latest/operations/meta-monitoring/mixins/).