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 upDon't do incremental backoffs on unhealthy targets? #302
Comments
This comment has been minimized.
This comment has been minimized.
|
+1 |
This comment has been minimized.
This comment has been minimized.
|
Fixed by @brian-brazil in 3835b75 |
juliusv
closed this
Aug 8, 2014
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 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 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedJun 13, 2013
The purpose of monitoring is also to see when a target was up or down, as precisely as possible. If we backoff on scraping unhealthy targets, we lose that information. Plus, the "up = 0" timeseries for a target may go stale if the backoff period is larger than the staleness allowance.