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
default_rollup
last_over_time
From the current(2024-05-15) MetricsQL documentation, it seems that the default_rollup and last_over_time functions are effectivly the same.
Even looking into the code, those functions seem the same
VictoriaMetrics/app/vmselect/promql/rollup.go
Line 2328 in 5e8c087
But there are somewhat hidden differences at minimum with staleness marker handling, which are non-obvious
VictoriaMetrics/app/vmselect/promql/eval.go
Line 1972 in 5e8c087
Those differences, as well as any other differences, should be documented in the MetricsQL documentation.
The text was updated successfully, but these errors were encountered:
hey @michalhosna thanks for a finding added PR with a note about difference between these functions
Sorry, something went wrong.
docs: added information about difference between default_rollup and l…
ce3cfd7
…ast_over_time (#6282) #6279
Thanks for reporting @michalhosna! The issue should be addressed in this commit ce3cfd7
23c7193
…ast_over_time (#6282) #6279 (cherry picked from commit ce3cfd7)
Successfully merging a pull request may close this issue.
From the current(2024-05-15) MetricsQL documentation, it seems that the
default_rollup
andlast_over_time
functions are effectivly the same.Even looking into the code, those functions seem the same
VictoriaMetrics/app/vmselect/promql/rollup.go
Line 2328 in 5e8c087
But there are somewhat hidden differences at minimum with staleness marker handling, which are non-obvious
VictoriaMetrics/app/vmselect/promql/eval.go
Line 1972 in 5e8c087
Those differences, as well as any other differences, should be documented in the MetricsQL documentation.
The text was updated successfully, but these errors were encountered: