You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some metrics with very high cardinality, which causing recording rules for longer periods (2h+ to timeout or simply run our Prometheus instance very high on CPU.
I would like to chain recording rules all based on 5m rule, without overwriting every record rule manually in the yaml.
example for 30m record rule to be based on 5 min rule (al lthe others 1h, 2h,6h,1d,3d,1w would follow the same pattern).
We have some metrics with very high cardinality, which causing recording rules for longer periods (2h+ to timeout or simply run our Prometheus instance very high on CPU.
I would like to chain recording rules all based on 5m rule, without overwriting every record rule manually in the yaml.
example for 30m record rule to be based on 5 min rule (al lthe others 1h, 2h,6h,1d,3d,1w would follow the same pattern).
The text was updated successfully, but these errors were encountered: