From 2be67be042028ba094a385210ae3687ac86c0785 Mon Sep 17 00:00:00 2001 From: Aman <95525722+amanycodes@users.noreply.github.com> Date: Fri, 28 Mar 2025 23:45:59 +0530 Subject: [PATCH] docs: remote-write-receiver explicit flag enablement (#16214) * docs: remote-write-receiver explicit flag enablement Signed-off-by: amanycodes * Rebuild Signed-off-by: amanycodes * updated docs/migration.md Signed-off-by: amanycodes --------- Signed-off-by: amanycodes --- docs/migration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/migration.md b/docs/migration.md index 44cd466b3d..d9a1148951 100644 --- a/docs/migration.md +++ b/docs/migration.md @@ -15,7 +15,6 @@ This document offers guidance on migrating from Prometheus 2.x to Prometheus 3.0 default behavior of Prometheus v3: - `promql-at-modifier` - `promql-negative-offset` - - `remote-write-receiver` - `new-service-discovery-manager` - `expand-external-labels` - Environment variable references `${var}` or `$var` in external label values @@ -31,6 +30,8 @@ This document offers guidance on migrating from Prometheus 2.x to Prometheus 3.0 `http://example.com/metrics:80` respectively, add them to your target URLs - `agent` - Instead use the dedicated `--agent` CLI flag. + - `remote-write-receiver` + - Instead use the dedicated `--web.enable-remote-write-receiver` CLI flag to enable the remote write receiver. - `auto-gomemlimit` - Prometheus v3 will automatically set `GOMEMLIMIT` to match the Linux container memory limit. If there is no container limit, or the process is