Julien

Labels have to be sorted. Prometheus is doing it when it e.g. scrapes: https://github.com/prometheus/prometheus/blob/b1566f761ef7d1c8ab6446afd017c0ce17e9224e/model/textparse/promparse.go#L239

We have optimisations that depend on ordering. PromQL does not work on unsorted labels. Le vendredi 11 novembre 2022, Bryan Boreham ***@***.***> a écrit : > This is very clear...

This is a change from go1.19: > Resolver.PreferGo is now implemented on Windows and Plan 9. It previously only worked on Unix platforms. Combined with Dialer.Resolver and Resolver.Dial, it's now...

I don't like mixing 2021-12-01/compute and 2018-10-01/network. I think someone should tackle https://github.com/prometheus/prometheus/issues/10942 instead

Sounds like there is consensus on the mailing list

Thanks for your pull request. I think that instead of supporting passwords on the command line, promtool should take a yaml config file as input, with the same TLS client...

> Just to make sure that I understand correctly, which passwords are you referring to? > The PR adds three arguments, which are file paths to key-file, cert-file and cacert-file....

https://github.com/prometheus/alertmanager/pull/2391

I am not sure if this should be covered here or in the docs repository directly. Additionally, chmod 777 is a security issue.

I wonder if everything needs to be put down under a if or if we should adapt the exiting ifs with the variable