Question & Answer
Question
I'm interested in updating the scrape_configs definitions, and this was previously done by customizing prometheus.yaml file.
In IBM Cloud Private 3.2.0 the prometheus.yaml could be customized as follows:
kubectl edit cm monitoring-prometheus
In IBM Cloud Private 3.2.2 this is no longer possible.
I have tried it as follows:
kubectl get secret prometheus-monitoring-prometheus -o yaml > prometheus-monitoring-prometheus.yaml
echo "<encoded-value>" | base64 -d > prometheus.yaml.gz
gunzip prometheus.yaml.gz
edit prometheus.yaml
gzip prometheus.yaml
cat prometheus.yaml.gz | base64 -w 0
kubectl edit secret prometheus-monitoring-prometheus
But changes are reset to default by IBM Cloud Private and the customization is not applied.
Why does it happen?
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"ARM Category":[{"code":"a8m0z000000cvtsAAA","label":"IBM Cloud Private-\u003EMonitoring"}],"ARM Case Number":"TS004147999","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Product Synonym
IBM Cloud Private;ICP
Was this topic helpful?
Document Information
Modified date:
13 October 2020
UID
ibm16346844