-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
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
promql query over recent data is missing points #2191
Comments
I don't see this in rc2; possibly fixed, closing for now. |
Nah, still occurs, dunno what affects when it does or not. |
Still in rc3. |
Seems to be mostly fixed in rc4, although there's still one case in which this happens:
datapoints inserted at RF=1 will be returned in some query results but not all (so redoing query will sometimes return only RF=3 points, and sometimes earlier ones with RF=1 too). Is this intended behavior? ( @robskillington ) |
Fixed by M3 0.15 release. |
Component: m3coordinator
Version: 0.15rc1
Configuration (probably only namespace relevant):
Ok, so I'm having rather weird problem with 0.15rc1; hopefully it is just matter of my ignorance.
Given short (1 hour) window over the very recent data, I get no results.
curl "${M3C_URL}/api/v1/query_range?query=avg%20by%20(host)(system_load1%7Bservice_id%3D~'116611'%7D)&start=1583309220&end=1583312820&step=15" | python3 -m json.tool
Then, if I increase the data to roughly 4 hours still with step=15 (only changing the
start
parameter to smaller value), I get results..curl "${M3C_URL}/api/v1/query_range?query=avg%20by%20(host)(system_load1%7Bservice_id%3D~'116611'%7D)&start=1583300000&end=1583312820&step=15" | python3 -m json.tool
some of them within the last 1 hour that returned nothing before.
..
1583312780
..
1583312810
Am I misunderstanding something about how the prom query endpoint should work, or is this a bug?
The text was updated successfully, but these errors were encountered: