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 upThe list of dropped targets grows forever #3652
Comments
This comment has been minimized.
This comment has been minimized.
|
IIUC we're accumulating dropped targets and the list is never reset. See prometheus/retrieval/scrape.go Line 263 in ec94df4 |
This comment has been minimized.
This comment has been minimized.
|
cc @Conorbro |
This comment has been minimized.
This comment has been minimized.
|
Thanks, I'll take a look now. |
brancz
closed this
in
#3655
Jan 17, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
simonpasquier commentedJan 4, 2018
What did you do?
Setup Prometheus with kubernetes_sd scrape configuration. Then go to the Status > Service discovery page in the Prometheus UI.
What did you expect to see?
The list of targets including those which have been dropped.
What did you see instead? Under which circumstances?
The list of dropped targets is larger than what it should be and continues to grow over time.
Environment
Linux 4.4.0-104-generic x86_64
prometheus, version 2.0.0 (branch: master, revision: ec94df4)
build user: pasquier-s@simon-trusty
build date: 20180104-09:35:39
go version: go1.9.2