prometheus/config/testdata/remote_write_dup.bad.yml at c5a832b39440547f681dc08f06343c79d5ba7f45 - mudhorn/prometheus - Forgejo: Beyond coding. We forge.

mudhorn/prometheus

mirror of https://github.com/prometheus/prometheus.git synced 2024-11-10 07:34:04 -08:00

Callum Styan 67838643ee

Add config option for remote job name (#6043 )

* Track remote write queues via a map so we don't care about index.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Support a job name for remote write/read so we can differentiate between
them using the name.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Remote write/read has Name to not confuse the meaning of the field with
scrape job names.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Split queue/client label into remote_name and url labels.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Don't allow for duplicate remote write/read configs.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Ensure we restart remote write queues if the hash of their config has
not changed, but the remote name has changed.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

* Include name in remote read/write config hashes, simplify duplicates
check, update test accordingly.

Signed-off-by: Callum Styan <callumstyan@gmail.com>

2019-12-12 12:47:23 -08:00

7 lines

97 B

YAML

Raw Blame History

 remote_write:
   - url: localhost:9090
     name: queue1
   - url: localhost:9091
     name: queue1