Repository: prometheus/prometheus (language: go)

Issue:
Configurabe scrape interval / scrape timeout via relabeling still marked as experimental
### Proposal

Hello,
the possibility of configuring scrape_interval/scrape_timeout via relabeling has been implemented in #8911 which was merged in Aug, 2021, roughly 2.5 years ago. Still the feature is marked as "experimental". This seems to be the case only in the documentation, I did not find anything in the code that marks the feature as experimental, it isn't hidden behind a feature flag either.
I haven't been able to find any issues caused by this feature (and I'm currently using it myself successfully), so I'd propose to remove the hint in the docs telling users that it is experimental. Or are there any objections to that which I'm not aware of?

Thanks in advance,
Sven


Discussion / hints:
Hello Sven,

Yes, this feature can be marked as stable.

Fix patch:
diff --git a/docs/configuration/configuration.md b/docs/configuration/configuration.md
index 010a454661a..51eb84ae196 100644
--- a/docs/configuration/configuration.md
+++ b/docs/configuration/configuration.md
@@ -3236,7 +3236,7 @@ are set to the scheme and metrics path of the target respectively. The `__param_
 label is set to the value of the first passed URL parameter called `<name>`.
 
 The `__scrape_interval__` and `__scrape_timeout__` labels are set to the target's
-interval and timeout. This is **experimental** and could change in the future.
+interval and timeout.
 
 Additional labels prefixed with `__meta_` may be available during the
 relabeling phase. They are set by the service discovery mechanism that provided


Test patch: