Skip to content
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

Choose lowest downsampling resolution with granular control. #1465

Closed
wants to merge 1 commit into from

Conversation

bwplotka
Copy link
Member

Playing with Select storage.SelectParams.Step

As a follow up on this: #1431 I was experimenting with subquery + resolution in order to automatically adjust what downsampling Thanos should use. This, in theory, sounds great but looks like I don't really understand PromQL storage.Params.Step field properly. Need to investigate more (is this param not propagated)?

TODO:

  • [] Proper design
  • [] Investigate why the step is not propagated from [...:<resolution>]

Signed-off-by: Bartek Plotka bwplotka@gmail.com

Signed-off-by: Bartek Plotka <bwplotka@gmail.com>
},
},
{
query: "rate(up[5m:200s])",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not work as expected (in my mind). Step is still passed as 100 ms no matter what. cc @brian-brazil for help =D

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The step is the one for query_range. We're not passing any hints relating to subqueries currently.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Will look deeper in PromQL if it's sane to actually propagate that hint & how.

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 11, 2020
@stale stale bot closed this Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants