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 upRecord rules results shifted in time #5307
Comments
This comment has been minimized.
This comment has been minimized.
|
Can you share your recording rules file? |
simonpasquier
added
component/rules
kind/more-info-needed
labels
Mar 5, 2019
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
kminehart
commented
Mar 7, 2019
|
This is similar to: I believe we were experiencing the same sort of time drift problem, but we have way too many recording rules, and a lot of them are fairly complex (most of them came with the prometheus operator), so we might have been experiencing an even greater amount of it. |
geekodour
referenced this issue
Apr 10, 2019
Open
Compared versions are not queried at the same rate. #173
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
alex-k commentedMar 5, 2019
•
edited
Bug Report
What did you do?
I have two recording rules
What did you expect to see?
I expect to see in result same values as in target metrics grouped by labels
What did you see instead? Under which circumstances?
Sometimes I see values shifted in time by 15sec
Expected:
Got:
Environment
Not applicable
Not applicable
Version 2.6.1
Revision b639fe1
Not applicable
Prometheus configuration file:
Alertmanager configuration file:
Logs: