Julien Leloup

I am also interested by such feature though it would be to use a `prevent_destroy` lifecycle directive.

I happen to have the same behaviour on my clusters since the v0.23.1 update. Rollbacking Thanos Ruler to 0.22.0 did the trick for us to work around this issue. Maybe...

[thanos-rule.pprof.txt](https://github.com/thanos-io/thanos/files/7642335/thanos-rule.pprof.txt) This is from one of our Thanos Ruler currently failing to process some records (I haven't figured out yet if this applies to all of them or not). Version...

One lead we are testing right now for this issue: fine tuning Thanos Query & Query Frontend. We have increased some concurrency parameters & the likes to ensure that there...

Update: increasing Thanos Query performances helped for some time but eventually our Thanos Rule instances ends up evaluating no rules at all. The only thing I can add is that...

This issue also happens when you use both Flux v1 and Flux v2 (during migration for example) as both provides a HelmChart CRD though in different groups.

To add to the discussion, having a way to keep a Prometheus label as part of the aggregation would also help with keeping some extra labels in alerts. For example...

Would using Loki metrics generator be a suitable solution for this problem ? My understanding is that SLOs & SLAs are numeric by nature, thus having a first step transforming...

A similar use cas I have that could benefit from having external labels set bu Mimir Ruler: I am using [Sloth](https://sloth.dev/) to produce PrometheusRules resources which are then loaded into...

In addition to @mike-brown-angi answer: you could use Grafana Agent [mimir.rules.kubernetes](https://grafana.com/docs/agent/latest/flow/reference/components/mimir.rules.kubernetes/) to fetch the PrometheusRules created by a Sloth running there into Grafana Mimir. A similar setup can be achieved...