[enterprise-4.12] Issue in file monitoring/configuring-the-monitoring-stack.adoc #57544
Description
Which section(s) is the issue in?
https://docs.openshift.com/container-platform/4.12/monitoring/configuring-the-monitoring-stack.html
What needs fixing?
There is conflicting or unclear information with regard to custom alertmanager configs. In one section it is mentioned, that these should be made in a secret resource and in another section, it's a ConfigMap. This should be clarified.
Example:
To configure core OpenShift Container Platform monitoring components, you must create the cluster-monitoring-config ConfigMap object in the openshift-monitoring project.
The Alertmanager configuration is deployed as a secret resource in the openshift-monitoring namespace. If you have enabled a separate Alertmanager instance for user-defined alert routing, an Alertmanager configuration is also deployed as a secret resource in the openshift-user-workload-monitoring namespace. To configure additional routes for any instance of Alertmanager, you need to decode, modify, and then encode that secret. This procedure is a supported exception to the preceding statement.