-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[prometheusreceiver] Handle staleNaN for up
metric
#9253
Conversation
Noooooope, closing this because NaN is never exposed via I have another idea as to what might cause #5249, will investigate that. |
e32d073
to
c4d71d8
Compare
DONOT MERGE: Depends on prometheus/prometheus#10588 being merged. But once the above PR is merged, we will see the error in #5249 whenever a target goes away (I've verified it). I've fixed it here and will make the PR ready once upstream PR is merged. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
When a target disappears, a StaleNaN is added. We should handle that case too. Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
c4d71d8
to
4d4efa9
Compare
Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice find
…9253) * [prometheusreceiver] Handle staleNaN for up metric When a target disappears, a StaleNaN is added. We should handle that case too. Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com> Co-authored-by: Alex Boten <aboten@lightstep.com>
Fixes #5249
TODO: