github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: clarify that auto generated metrics can't be relabeled in scrape config

Browse source 
Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
hagen1778 2024-10-24 12:09:30 +02:00
parent ec0abe736a
commit 53b7288e0d
No known key found for this signature in database
GPG key ID: E92986095E0DD614
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/vmagent.md
View file

@ -567,6 +567,8 @@ and attaches `instance`, `job` and other target-specific labels to these metrics
If the target exports metrics with names clashing with the automatically generated metric names, then `vmagent` automatically If the target exports metrics with names clashing with the automatically generated metric names, then `vmagent` automatically
adds `exported_` prefix to these metric names, so they don't clash with automatically generated metric names. adds `exported_` prefix to these metric names, so they don't clash with automatically generated metric names.
Relabeling defined in `relabel_configs` or `metric_relabel_configs` of scrape config isn't applied to automatically
generated metrics. But they still can be relabeled via `-remoteWrite.relabelConfig` before sending metrics to remote address.
## Relabeling ## Relabeling