A specific parameter for additional remote writes

[abjrcode]

Why is it not possible to add additional remoteWrites just like it is the case for additionalServiceMonitors?

The documentation on scraping additional services now points to the prometheus-overrides.yaml file, but that is error prone as I need to (possibly) re-generate it on chart updates?

Basically it would be nice to add additional monitors and remote writes without touching the ones provided by Sumo (just augmenting them).

[abjrcode]

Something to consider, I and probably most others implement this with GitOps and want to avoid running any commands manually if possible.

[perk-sumo]

Hi, the reason for that is because the Kube Prometheus Stack subchart we use doesn't provide such possibility - there is only one section for the remoteWrite to be used:
https://github.com/prometheus-community/helm-charts/blob/kube-prometheus-stack-12.3.0/charts/kube-prometheus-stack/values.yaml#L1943

We know it's not ideal.

[abjrcode]

Thanks for the clarification. Wouldn't be possible that you expose this as a parameter on your own chart and then merge the result when passing it to the subchart?

[sumo-drosiek]

Wouldn't be possible that you expose this as a parameter on your own chart and then merge the result when passing it to the subchart?

We are not aware of possibility to do that and keep everything clean and simple

We created PR in the kube-prometheus-stack helm chart, so maybe we will be able to do it in a proper way 🤞

[sumo-drosiek]

labeling as breaking-change, because it requires updating the Prometheus CRDs