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 upNon negligible divergence between recorded metric and original expression #1832
Comments
This comment has been minimized.
This comment has been minimized.
|
Given the default eval interval is 1m and you're scraping every 15s, this is an expected result when using |
This comment has been minimized.
This comment has been minimized.
|
Thank you Brian, I'lll close this issue as I'm not working on it anymore. |
noushi
closed this
Jul 25, 2016
noushi
referenced this issue
Aug 9, 2016
Closed
Faster query processing using old expression than new one with recorded rule #1829
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.
noushi commentedJul 20, 2016
What did you do?
To speed up console node list, I created a record rule:
What did you expect to see?
I expected the recorded metric to be almost identical to the original expression.
What did you see instead? Under which circumstances?
Instead, graphing
shows a divergence of more than 20% on multiple occasions:


DISCLAIMER: The server showing the highest divergence is one our most busiest.
Environment
I'm using a Docker container.
From
/status:I didn't see any relevant entries.