Hello. The answer is actually rather short: You cannot use the Prometheus/alertmanger supplied with openshift for application monitoring.
We’ve set up a second prometheus/alertmanager instance in its own namespace that is used for all application monitoring. Regards Kristian [cid:imagec359aa.PNG@3ca73523.48aada1c] Kristian Ejvind Linux System Administrator IT Operations | Technical Operations Resurs Bank Ekslingan 8 Box 222 09, SE-25467 Helsingborg Mobil: +46 728571483 Växel: +46 42 38 20 00 E-post: kristian.ejv...@resurs.se<mailto:kristian.ejv...@resurs.se> Webb: www.resursbank.se<http://www.resursbank.se> From: <users-boun...@lists.openshift.redhat.com> on behalf of SUBASHI Aida <suba...@scigames.at> Date: Monday, 11 May 2020 at 15:24 To: "users@lists.openshift.redhat.com" <users@lists.openshift.redhat.com> Subject: how to edit prometheus-k8s-rulefiles-0 config-map in OCP-3.11 Dear all, We are looking to create a custom rule for Prometheus to generate alerts for other new namespaces that we create. When I update the prometheus-k8s-rulefiles-0 config-map, my changes are not retained. The config map is not possible to change based on our neeeds. How can I make changes so that we can use the existing Prometheus/Alert Manager installed with OpenShift 3.11? I will appreciate any technical suggestion. BR, ___________________________________________ Aida SUBASHI | DevOps Specialist | Scientific Games International GmbH<https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.scigames.at&umid=06d8a303-e2d4-46c7-8062-9e7f9a59bdbe&auth=daed959355609b907128d19d56c675829c94a38e-020ba58a8ecd9ae2eea0da7f672f1244b762ebc0> | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee.
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
