openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

OBSDOCS-197: Clarify information about secrets in custom Alertmanager configs

Browse Source
This commit is contained in:
Eliska Romanova
2024-03-26 11:32:21 +01:00
committed by openshift-cherrypick-robot
parent b21e2d66e0
commit 6eea6e2e02
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/monitoring-creating-cluster-monitoring-configmap.adoc
View File

@@ -6,7 +6,7 @@
[id="creating-cluster-monitoring-configmap_{context}"]
= Creating a cluster monitoring config map
To configure core {product-title} monitoring components, you must create the `cluster-monitoring-config` `ConfigMap` object in the `openshift-monitoring` project.
You can configure the core {product-title} monitoring components by creating the `cluster-monitoring-config` `ConfigMap` object in the `openshift-monitoring` project. The Cluster Monitoring Operator (CMO) then configures the core components of the monitoring stack.
[NOTE]
====

2
modules/monitoring-creating-user-defined-workload-monitoring-configmap.adoc
View File

@@ -6,7 +6,7 @@
[id="creating-user-defined-workload-monitoring-configmap_{context}"]
= Creating a user-defined workload monitoring config map
To configure the components that monitor user-defined projects, you must create the `user-workload-monitoring-config` `ConfigMap` object in the `openshift-user-workload-monitoring` project.
You can configure the user workload monitoring components by creating the `user-workload-monitoring-config` `ConfigMap` object in the `openshift-user-workload-monitoring` project. The Cluster Monitoring Operator (CMO) then configures the components that monitor user-defined projects.
[NOTE]
====

4
modules/monitoring-support-considerations.adoc
View File

@@ -14,8 +14,8 @@ ifndef::openshift-dedicated,openshift-rosa[]
+
[NOTE]
====
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.
The Alertmanager configuration is deployed as the `alertmanager-main` 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 the `alertmanager-user-workload` 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.
====

2
monitoring/configuring-the-monitoring-stack.adoc
View File

@@ -37,7 +37,7 @@ ifndef::openshift-dedicated,openshift-rosa[]
[id="preparing-to-configure-the-monitoring-stack"]
== Preparing to configure the monitoring stack
You can configure the monitoring stack by creating and updating monitoring config maps.
You can configure the monitoring stack by creating and updating monitoring config maps. These config maps configure the Cluster Monitoring Operator (CMO), which in turn configures the components of the monitoring stack.
include::modules/monitoring-creating-cluster-monitoring-configmap.adoc[leveloffset=+2]
include::modules/monitoring-creating-user-defined-workload-monitoring-configmap.adoc[leveloffset=+2]