prometheus/scrape
Krasi Georgiev 47a673c3a0
process scrape loops reloading in parallel (#4526)
The scrape manage receiver's channel now just saves the target sets
and another backgorund runner updates the scrape loops every 5 seconds.
This is so that the scrape manager doesn't block the receiving channel
when it does the long background reloading of the scrape loops.

Active and dropped targets are now saved in each scrape pool instead of
the scrape manager. This is mainly to avoid races when getting the
targets via the web api.

When reloading the scrape loops now happens in parallel to speed up the
final disared state and this also speeds up the prometheus's shutting
down.

Also updated some funcs signatures in the web package for consistency.

Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com>
2018-09-26 12:20:56 +03:00
..
testdata
helpers_test.go
manager.go process scrape loops reloading in parallel (#4526) 2018-09-26 12:20:56 +03:00
manager_test.go process scrape loops reloading in parallel (#4526) 2018-09-26 12:20:56 +03:00
scrape.go process scrape loops reloading in parallel (#4526) 2018-09-26 12:20:56 +03:00
scrape_test.go process scrape loops reloading in parallel (#4526) 2018-09-26 12:20:56 +03:00
target.go scrape,api: provide per-target metric metadata 2018-06-06 05:56:10 -04:00
target_test.go support reading basic_auth password_file for HTTP basic auth (#4077) 2018-04-25 18:19:06 +01:00