-
Notifications
You must be signed in to change notification settings - Fork 129
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
Add support for various timeranges associated with ServerGroups #88
Comments
With the more recent rearch inside servergroup this is a trivial add to make, at this point I just need to decide on the config format. I'm thinking having absolute time is probably not useful -- so I'll set it up as relative times. The config formats I'm thinking of now are:
|
After some more thought, I'm planning on adding 2 time range options:
And for both of these if the window is invalid (e.g. start after end) there'll be an error. |
This adds 2 optional config flags to a servergroup; relative_time_range and absolute_time_range. Both of these provide a way to scope the timerange of a given servergroup such that if a query is outside the time window promxy will not query the given servergroup. Implements #88
This adds 2 optional config flags to a servergroup; relative_time_range and absolute_time_range. Both of these provide a way to scope the timerange of a given servergroup such that if a query is outside the time window promxy will not query the given servergroup. Implements #88
#162 Implements this |
The goal here being to support sending queries to separate stacks of metrics storage based on their "staleness". The prom API unfortunately doesn't expose the
StartTime()
method from theStorage
-- so we'd need to add config options to set atime.Duration
offset and duration for each servergroup. Then promxy can add this dimension to its filtering for where to send queries to.The text was updated successfully, but these errors were encountered: