mirror of
https://github.com/prometheus/prometheus.git
synced 2025-02-02 08:31:11 -08:00
Merge pull request #5728 from prometheus/beorn7/doc
Clarifying honor_labels documentation
This commit is contained in:
commit
52e28b41d3
|
@ -127,8 +127,11 @@ job_name: <job_name>
|
||||||
# If honor_labels is set to "false", label conflicts are resolved by renaming
|
# If honor_labels is set to "false", label conflicts are resolved by renaming
|
||||||
# conflicting labels in the scraped data to "exported_<original-label>" (for
|
# conflicting labels in the scraped data to "exported_<original-label>" (for
|
||||||
# example "exported_instance", "exported_job") and then attaching server-side
|
# example "exported_instance", "exported_job") and then attaching server-side
|
||||||
# labels. This is useful for use cases such as federation, where all labels
|
# labels.
|
||||||
# specified in the target should be preserved.
|
#
|
||||||
|
# Setting honor_labels to "true" is useful for use cases such as federation and
|
||||||
|
# scraping the Pushgateway, where all labels specified in the target should be
|
||||||
|
# preserved.
|
||||||
#
|
#
|
||||||
# Note that any globally configured "external_labels" are unaffected by this
|
# Note that any globally configured "external_labels" are unaffected by this
|
||||||
# setting. In communication with external systems, they are always applied only
|
# setting. In communication with external systems, they are always applied only
|
||||||
|
|
Loading…
Reference in a new issue