When scaling Promitor, I want to keep the metrics declaration outside of values.yaml and point the Scraper to a mounted file via runtime config, as described in the docs: https://docs.promitor.io/latest/scraping/runtime-configuration/#metric-configuration
metricsConfiguration:
absolutePath: /config/metrics-declaration.yaml # Optional. Default: /config/metrics-declaration.yaml
However, this setting appears to be ignored by the Helm chart. The generated manifests/configmaps do not reflect this runtime option, and the Scraper continues to look only at the default location bundled with the chart values (/config/*). The Helm chart does not template or propagate metricsConfiguration.absolutePath into the Scraper’s runtime configuration/configmap, as seen here: https://github.com/promitor/charts/blob/main/promitor-agent-scraper/templates/configmap.yaml#L59-L60
I would like to propose a PR to add support for this.
It should be very simple change to the configmap.yaml template.
When scaling Promitor, I want to keep the metrics declaration outside of values.yaml and point the Scraper to a mounted file via runtime config, as described in the docs: https://docs.promitor.io/latest/scraping/runtime-configuration/#metric-configuration
However, this setting appears to be ignored by the Helm chart. The generated manifests/configmaps do not reflect this runtime option, and the Scraper continues to look only at the default location bundled with the chart values (/config/*). The Helm chart does not template or propagate metricsConfiguration.absolutePath into the Scraper’s runtime configuration/configmap, as seen here: https://github.com/promitor/charts/blob/main/promitor-agent-scraper/templates/configmap.yaml#L59-L60
I would like to propose a PR to add support for this.
It should be very simple change to the configmap.yaml template.