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 upoffset keyword not working in recorded rules or alert rules #1223
Comments
brian-brazil
closed this
in
#1224
Nov 15, 2015
brian-brazil
referenced this issue
Nov 23, 2015
Closed
offset not honored with recording rules #1234
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 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. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
jamessanford commentedNov 15, 2015
Having problems with "offset" in recorded rules and alerts.
Full expression works in templates and expression browser, but when a recorded rule or alert rule, "offset" gets ignored.
For example, with these two rules. Evaluating the two new timeseries in the browser, they always report the same number -- and on the status page rule list there's no mention of "offset"
Screenshot of status page, note missing "offset" keyword on the right hand side:
Screenshot of first rule:
Screenshot of offset rule, note that the value is reported as the same, it should not be:
Evaluating the expression in the browser itself works, and the "offset" version does report the offset:
The above examples use "offset 1m", but the same issue persists with 5m, 30m, ... the recorded rules don't use the offset.
(fyi this test prometheus instance has scrape/evaluation intervals of 5s)