feat: adjustable rule_group interval #515
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows for more expensive SLO recording rules by letting users
create a custom Prometheus
rule_group.interval
, as rule group default or per type of rule.https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/#rule_group
Now instead of all rule groups using the default global evaluation
interval, a custom interval can be set on all three types of recording rules
for an SLO.
If no
interval
is set then the global default will be assumed,matching current Sloth behavior.
Resolves: #367
Edit: I didn't touch the kubernetes operator side and probably need adjustments there