I readed in: https://www.percona.com/blog/2020/03/23/extending-pmm-prometheus-configuration/
In the next release, we will use our own code for configuration parser. It is a separate Go library that can be useful for the community.
I have updated today my PMM2 server and i get yml parsing errors:
/srv/logs/pmm-managed.log line 21: cannot unmarshal !!seq into string line 41: cannot unmarshal !!seq into string line 43: cannot unmarshal !!seq into string line 45: cannot unmarshal !!seq into string
That lines are relabeling ones in my custom prometheus configuration file:
/srv/prometheus/prometheus.base.yml [root@3550a92c2086 opt]# cat /srv/prometheus/prometheus.base.yml --- scrape_configs: - job_name: blackbox80 params: module: - http_2xx scrape_interval: 1m scrape_timeout: 10s metrics_path: /probe scheme: http static_configs: - targets: - www.alfaexploit.com metrics_path: "/archive" relabel_configs: - source_labels: [__address__] target_label: __param_target - source_labels: [__param_target] target_label: instance - source_labels: [__param_target] target_label: node_name - target_label: __address__ replacement: grafana2.adsalsa.net:9115
In previous version it worked without problems.
Is it broken, is there another way to do relabeling with that new PMM2 version?