We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
offset
Describe the bug after upgrade vmselect from 6f1d926 to 4353ff7 the result of offset is abnormal i think it relate to 17f175f ?
To Reproduce q offset 24h from today 00:00 to today 24:00, the result is odd. from now() to 24:00 is a straight line
q offset 24h
today 00:00
today 24:00
now()
24:00
Expected behavior the result of q offset 24h from 00:00 to 24:00 is equal to q from 00:00 - 24h to 24:00 -24h
00:00
q
00:00 - 24h
24:00 -24h
Screenshots
Version
$ ./vmselect-prod -version vmselect-20200713-124700-heads-cluster-0-g4353ff7e
The text was updated successfully, but these errors were encountered:
app/vmselect/prometheus: do not adjust last points in time series wit…
0e7b200
…h timestamps exceeding the current time Such timestamps usually mean that the query contains `offset`. See #625
25f80d3
@n4mine , thanks for the bug report! The bug should be fixed in the commit 0e7b200 .
Sorry, something went wrong.
confirm, thanks @valyala
The bugfix has been included in v1.38.1 release.
No branches or pull requests
Describe the bug
after upgrade vmselect from 6f1d926 to 4353ff7
the result of
offset
is abnormali think it relate to 17f175f ?
To Reproduce
q offset 24h
fromtoday 00:00
totoday 24:00
, the result is odd.from
now()
to24:00
is a straight lineExpected behavior
the result of
q offset 24h
from00:00
to24:00
is equal toq
from00:00 - 24h
to24:00 -24h
Screenshots
Version
The text was updated successfully, but these errors were encountered: