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.

Sign up for GitHub

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

Jump to bottom

Add operator that supports getting ranges at intervals #89

Closed
juliusv opened this issue Mar 21, 2013 · 4 comments
Closed

Add operator that supports getting ranges at intervals #89

juliusv opened this issue Mar 21, 2013 · 4 comments
Assignees
@matttproud

Comments

@juliusv
Copy link
Member

juliusv commented Mar 21, 2013

If a query resolution is lower (e.g. 5m) than a metric range (like foo[1m]) requested in a query, we actually need to fetch ranges at repeated intervals so as not to fetch too much data.
@ghost ghost assigned matttproud Mar 21, 2013
@juliusv
Copy link
Member Author

juliusv commented Jun 17, 2013

Also, having one range-at-interval-op for each entire timeseries is going to be faster and more memory-efficient than one per target point in the timeseries.

@juliusv
Copy link
Member Author

juliusv commented Jun 28, 2013

Operator implemented in d2da211 - disabled optimize() phase... we might have to revisit whether to keep/properly implement the optimization phase later, so keeping this open for now.

@juliusv
Copy link
Member Author

juliusv commented May 23, 2014

We decided we'll not need the optimize() phase again, so closing this.

@juliusv juliusv closed this as completed May 23, 2014
simonpasquier pushed a commit to simonpasquier/prometheus that referenced this issue Oct 12, 2017
@juliusv
Merge pull request prometheus#89 from prometheus/fabxc/getstarted
aceee04 
Adjust getting started section to new config format
@lock
Copy link

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 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.
Assignees

@matttproud matttproud

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matttproud @juliusv