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 upAlpha.2 Missing metrics on scrape when a sample limit is set (even when sample limit is not being actually hit) #2769
Comments
This comment has been minimized.
This comment has been minimized.
|
Do you know which metrics are missing? Is it always the same ones? |
brian-brazil
added
kind/bug
dev-2.0
labels
May 25, 2017
This comment has been minimized.
This comment has been minimized.
|
I believe they are the same metrics that are missing. The red line is my non-leader server which reports fewer metrics and notice how it is not showing the fluctuation. On the alpha.2 server there is a log line that corresponds to the dropped metrics of
So that would imply it is passing the 7500 limit I had set, but as we can see from the v1.6.2 server, there are <1000 metrics. Also The query |
This comment has been minimized.
This comment has been minimized.
|
Does the problem go away if you remove the limit? I see some issues with this code in 2.0, but nothing that'd cause this. |
This comment has been minimized.
This comment has been minimized.
|
Ah, we're passing along the wrong error message. |
brian-brazil
referenced this issue
May 25, 2017
Merged
Pass through storage errors in limitAppender. #2771
This comment has been minimized.
This comment has been minimized.
|
Removing the sample limit completely made the problem go away. Increasing the limit didn't work (though I had only tried tripling the value) |
checketts
changed the title
Alpha.2 Missing metrics on scrape
Alpha.2 Missing metrics on scrape when a sample limit is set (even when sample limit is not being actually hit)
May 25, 2017
This comment has been minimized.
This comment has been minimized.
|
Is this fixed with #2772 @brian-brazil |
This comment has been minimized.
This comment has been minimized.
|
No, I've got the code to fix just need to write the unittests. |
This comment has been minimized.
This comment has been minimized.
|
Fixed in #2787 |
fabxc
closed this
Jun 6, 2017
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. |
checketts commentedMay 25, 2017
•
edited
What did you do?
Running the
v2.0.0-alpha.2and comparing the results against my existingv1.6.2deploymentWhat did you expect to see?

Using
v1.6.2I can see the scrape samples coming in regularly with the queryscrape_samples_scraped{app="drydock"}What did you see instead? Under which circumstances?

With
alpha.2, scraping the same targets I see metrics being missedEnvironment
Running in Docker container in Kubernetes 1.4.1