From 57af4c66d1f2aa6b00f69dbfd7193b53784fd59c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miko=C5=82aj=20=C5=9Awi=C4=85tek?= Date: Mon, 25 Sep 2023 15:56:20 +0200 Subject: [PATCH] docs: update v4 migration doc --- docs/v4-migration-doc.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/v4-migration-doc.md b/docs/v4-migration-doc.md index ea72fa9fc0..2bd3fec8f0 100644 --- a/docs/v4-migration-doc.md +++ b/docs/v4-migration-doc.md @@ -83,21 +83,21 @@ There are several scenarios here, depending on the exact use case: 1. You're collecting different [Kubernetes metrics][kubernetes_metrics_v3] than what the Chart provides by default. You've modified the existing ServiceMonitor for these metrics, and added a remote write as instructed by the documentation. -You can safely delete the added remote write definition. No further action is required. + You can safely delete the added remote write definition. No further action is required. 1. As above, but you're also doing some additional data transformation via relabelling rules in the remote write definition. -You'll need to either move the relabelling rules into the ServiceMonitor itself, or [add an equivalent filter -processor][otel_metrics_filter] rule to Otel. + You'll need to either move the relabelling rules into the ServiceMonitor itself, or [add an equivalent filter + processor][otel_metrics_filter] rule to Otel. 1. You're collecting custom application metrics by adding a [`prometheus.io/scrape` annotation][application_metrics_annotation]. You don't need to filter these metrics. -No action is needed. + No action is needed. 1. As above, but you also have a remote write definition to filter these metrics. -You'll need to delete the remote write definition and [add an equivalent filter processor][otel_metrics_filter] rule to Otel. + You'll need to delete the remote write definition and [add an equivalent filter processor][otel_metrics_filter] rule to Otel. #### How do I revert to the v3 defaults?