Bartlomiej Plotka

No discussion yet, sorry for lag. From my understanding this feature only applies to managed GMP. One way of solving it is a new field e.g. "OperatorConfig.[ManagedAlertmanagerSpec](https://github.com/GoogleCloudPlatform/prometheus-engine/blob/8ef0ecbe8c204f3e31ea53b3f7867aa1d340f3ad/pkg/operator/apis/monitoring/v1/types.go#L167).Disabled = true that...

Note: @bernot-dev works on this feature (automatic disabling of AM and rule-eval if no configuration is used for those) 🤗

There is --rule flag: https://github.com/thanos-io/thanos/blob/79e70da702228ac0282fc7639f9f160d922b6dcb/cmd/thanos/query.go#L114-L113 We have now incident which we are handling with @moadz that adding stateless ruler as store potentially causes problems

And yes not finished `endpoints` work is extremely confusing

👋🏽 Thanks! First of all, it would be nice if you could upgrade to the latest client_golang. Then we might need to ask for some reproduction tests. @vesari actually found...

👋🏽 So Dosubot was kind of correct, it's [an intended and documented](https://pkg.go.dev/github.com/prometheus/[email protected]/prometheus#MetricVec.CurryWith) behavior of `CurryWith` method. > Curried and uncurried vectors behave identically in terms of collection. For your test...

Thanks! > Looking at prometheus/collectors, splitting it out doesn't remove any dependencies from the core module, so probably no value there. The thing is -- it's only because we forced...

Changed the title to focus on API move only. We could use that for mentorship project.

In my eyes there will just small and very often used portion of labels maintained by such filter, so it should be fine.

What exactly is not reproducible at the moment? Let's talk about specifics. I heard testing for certain Go version as a one thing.