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 upavg() doesn't deal with NaN's #4023
Comments
This comment has been minimized.
This comment has been minimized.
|
and if you wanted to create an alert if query has |
This comment has been minimized.
This comment has been minimized.
|
This is the correct behaviour. You are most likely aggregating incorrectly and trying to take an average of an average, which is statistically invalid. It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Mar 28, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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. |
zemek commentedMar 28, 2018
If you try to run
avg(query)on a query that returns someNaNvalues, the entire avg isNaN.It seems like it would be reasonable to just exclude these NaNs from the average so you don't have to do like
avg(query >= 0)or something more complicated if you want both positive/negative numbers.