-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
downsampling: Inconsistent query results on store data #376
Comments
You already narrowed it down, nice! ((: From logs, it looks like for 14d store is using RAW data and for 15d store is using downsampled data How to debug it?
Thanks for finding this! NOTE: Downsampled data needs to be carefully used (need |
@Bplotka you're right, using thanos-query ui and forcing raw-only data the queries are working as expected. My queries are not using _over_time, that must be the reason it's not working, I haven't found a way to combine irate and sum_over_time for plotting cpu usage... Maybe there's no bug them? Is it possible for us to make thanos stopping from downsampling results in the queries made by grafana? thanks! |
Not really, but it sounds like we can add some flag for it. But TBH using downsampling make sense, because you cannot even plot the all raw samples. I will add the flag for choosing default resolution mode for queries until we have some nice downsampling tutorial with examples. |
But still you should see something.. not empty results ): |
The reason I’m seeing empty results should be that I’m not using the
_over_time methods in the grafana query, does this make sense?
Thanks
…On Tue, 19 Jun 2018 at 13:07 Bartek Plotka ***@***.***> wrote:
But still you should see something.. not empty results ):
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#376 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARcVrMn2kZBLSV6S17yaY9ZX0_Bw5a1ks5t-SHZgaJpZM4UoZfb>
.
|
mhmhm, maybe - depends on your query. (: |
this is the query:
|
…rimental phase. (Details #376) Signed-off-by: Bartek Plotka <[email protected]>
…rimental phase. (Details #376) Signed-off-by: Bartek Plotka <[email protected]>
(Details #376) Signed-off-by: Bartek Plotka <[email protected]>
(Details #376) Signed-off-by: Bartek Plotka <[email protected]>
* query: Disable downsampling by default. (Details #376) Signed-off-by: Bartek Plotka <[email protected]> * docs: Updated component flags. (#411) Signed-off-by: Bartek Plotka <[email protected]>
Looks like old dup of: #396 which was fixed. (: |
*: get rid of store info api (thanos-io#7704)
Hi, I have a prometheus setup with 5 days retention and I'm seeing strange query results for intervals outside this range, see:
Query for k8s cpu usage now-14 days:
Everything is ok!
Now query for 15 days:
That's not ok, data that was present on the last query is not present in this one... what could be causing this?
thanos store log for 14 day query:
thanos store log for 15 days query:
are there any easy ways for debugging that?
thanks!
The text was updated successfully, but these errors were encountered: