Use remote_write to ship metrics from new or existing Prometheus installations

Instructions for configuring Prometheus and remote_write to ship metrics to Grafana Cloud vary depending on how you installed Prometheus into your Kubernetes clusters.

This section will show you how to configure remote_write for the following common deployment methods:

• Prometheus Operator deployed using either Prometheus Operator or the kube-prometheus stack. To learn how to do this, please see Configuring remote_write with Prometheus Operator.
• Prometheus Operator and kube-prometheus deployed using the Helm kube-prometheus-stack chart. To learn how to do this, please see Configuring remote_write with Helm and kube-prometheus-stack.
• Prometheus deployed using the Prometheus Helm chart. To learn how to do this, please see Configuring remote_write with Helm and Prometheus.
• Prometheus deployed using a Kubernetes Deployment and ConfigMap manifests. To learn how to do this, please see Configuring remote_write with a Prometheus ConfigMap.

If you’re starting from scratch and would like to install Prometheus Operator into a Kubernetes cluster and ship metrics to Grafana Cloud, please see:

• Migrating a Kube-Prometheus Helm stack. In this guide, you’ll learn how to install the kube-prometheus-stack Helm chart into your cluster, and ship its metrics to Grafana Cloud. You’ll also optionally learn how to allowlist metrics to reduce usage, and migrate dashboards and rules to Grafana Cloud.
• Installing Prometheus Operator with Grafana Cloud for Kubernetes. In this guide, you’ll install Prometheus Operator into a Kubernetes cluster (without Helm), configure it to scrape itself, and ships these metrics to Grafana Cloud.