Re: [prometheus-users] Oddity with v0.xxx tags

Yes, this is a workaround for Go major versioning changes. See: https://github.com/prometheus/prometheus/pull/12900 On Mon, Aug 19, 2024 at 8:52 PM 'Brian Candler' via Prometheus Users < prometheus-users@googlegroups.com> wrote: > I have just noticed a load of tags in the prometheus repo for v0.

[prometheus-users] Oddity with v0.xxx tags

I have just noticed a load of tags in the prometheus repo for v0.XXX (from v0.35.0 to v0.54.0 inclusiveq) which match with v2.XXX For example: https://github.com/prometheus/prometheus/tree/v0.54.0 https://github.com/prometheus/prometheus/releases/v0.54.0 and which github claims was only tagged l

[prometheus-users] Re: Questions about best way to monitor CPU usage and accuracy and container life-time

The @ modifier is no longer experimental. It was made a permanent part of Prometheus in Jan 2022, when the promql-at-modifier was made a no-op. It is no longer listed under feature flags . See commit b39f2739e5b01560ad8299d2579f1041a0

[prometheus-users] Re: Questions about best way to monitor CPU usage and accuracy and container life-time

I think I found one answer to question 2, which is to turn on this via " --enable-feature=promql-at-modifier" feature [1]. However, [2] says such " features .. are disabled by default since they are breaking changes or are considered experimental". So not sure if I want to use it. [1] https://pr