Aliaksandr Valialkin bf1869d33d lib/promscrape: allow overriding external_labels as Prometheus does ... Prometheus docs at https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config say: > In communication with external systems, they are always applied only > when a time series does not have a given label yet and are ignored otherwise. Though this may result in consistency chaos when scrape targets override `external_labels`, let's stick with Prometheus behavior for the sake of backwards compatibility. There is last resort in vmagent with `-remoteWrite.label`, which consistently sets the configured labels to all the metrics before sending them to remote storage. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/366		2020-03-12 20:25:27 +02:00
..
testdata	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
client.go	lib/promscrape: do not retry idempotent requests when scraping targets	2020-03-09 13:31:20 +02:00
config.go	lib/promscrape: allow overriding external_labels as Prometheus does	2020-03-12 20:25:27 +02:00
config_test.go	lib/promscrape: allow overriding external_labels as Prometheus does	2020-03-12 20:25:27 +02:00
scraper.go	lib/promscrape: remove possible races when registering and de-registering scrape workers for /targets page	2020-03-11 16:30:43 +02:00
scrapework.go	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
scrapework_test.go	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
scrapework_timing_test.go	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
statconn.go	app/vmagent: initial implementation for vmagent	2020-02-23 17:31:54 +02:00
targetstatus.go	lib/promscrape: consistently update /targets page after SIGHUP	2020-03-11 03:20:38 +02:00