docs: remove promscrape.dropOriginalLabels from relabeling-debug section

Follow-up for ef507d372b.

 It's no longer needed to manually set promscrape.dropOriginalLabels
 flag, since it's has False value by default.
This commit is contained in:
f41gh7
2026-04-15 12:28:06 +02:00
parent d3264bd78f
commit 3ae44e734b

View File

@@ -357,9 +357,6 @@ see two types of targets:
service discovery, before any relabeling rules are applied. This includes
targets that may later be dropped.
_This option is only available when the component is started with the
`-promscrape.dropOriginalLabels=false` flag._
{{% collapse name="How to use `/targets` page?" %}}
This `/targets` page helps answer the following questions:
@@ -379,18 +376,12 @@ to all metrics scraped from that target.
You can click the label column of the target to see the original labels
**before** any relabeling was applied.
_This option is only available when the component is started with the
`-promscrape.dropOriginalLabels=false` flag._
**3. Why does a target have a certain set of labels?**
Click the `target` link in the `debug relabeling` column. This opens a
step-by-step view of how the relabeling rules were applied to the original
labels.
_This option is only available when the component is started with the
`-promscrape.dropOriginalLabels=false` flag._
**4. How are metric relabeling rules applied to scraped metrics?**
Click the `metrics` link in the `debug relabeling` column. This shows how the
@@ -413,9 +404,6 @@ Each column on the page shows important details:
This page shows all
[discovered targets](https://docs.victoriametrics.com/victoriametrics/sd_configs/).
_This option is only available when the component is started with the
`-promscrape.dropOriginalLabels=false` flag._
It helps answer the following questions:
**1. Why are some targets dropped during service discovery or showing unexpected