Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPrometheus continues to scrape removed targets from empty scrape configs #4812
Comments
grobie
changed the title
Prometheus continues to scrape removed targets
Prometheus continues to scrape removed targets from empty scrape configs
Oct 31, 2018
This comment has been minimized.
This comment has been minimized.
|
I'll have a look at it. |
This comment has been minimized.
This comment has been minimized.
|
Edit: same behavior with 2.3 too. |
simonpasquier
referenced this issue
Nov 2, 2018
Merged
discovery: send empty group on empty SD config #4819
simonpasquier
closed this
in
#4819
Nov 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
grobie commentedOct 31, 2018
•
edited by beorn7
Bug Report
What did you do?
Removed last entry of a
static_configsdirective. Our template generator omits empty config blocks from being written out to disk. The written out scrape configuration didn't have any*_sd_configsorstatic_configsconfiguration block.What did you expect to see?
Either Prometheus rejects scrape configurations without a single discovery config (neither static nor any
*_sd_configs), or it handles such empty scrape configurations correctly.What did you see instead? Under which circumstances?
Prometheus didn't show any targets in the targets page, but continued to scrape the target from the last static_configs (with up == 0 as the target was deprovisioned).
Environment
System information:
Linux 4.18
Prometheus version:
2.4.2
@krasi-georgiev