Skip to content

Commit a1ff739

Browse files
committed
OBSDOCS-338-typo-fix-in-configuring-monitoring-stack
1 parent 0107f61 commit a1ff739

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

modules/monitoring-creating-cluster-id-labels-for-metrics.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@
88

99
You can create cluster ID labels for metrics for default platform monitoring and for user workload monitoring.
1010

11-
For default platform monitoring, you add cluster ID labels for metrics in the `write_relabel` settings for remote write storage in the `cluster-monitoring-config` config map in the `openshift-monitoring` namespace.
11+
For default platform monitoring, you add cluster ID labels for metrics in the `write_relabel` settings for remote write storage in the `cluster-monitoring-config` config map in the `openshift-monitoring` namespace.
1212

1313
For user workload monitoring, you edit the settings in the `user-workload-monitoring-config` config map in the `openshift-user-workload-monitoring` namespace.
1414

15-
.Prerequsites
15+
.Prerequisites
1616

1717
* You have installed the OpenShift CLI (`oc`).
1818
* You have configured remote write storage.
@@ -34,8 +34,8 @@ $ oc -n openshift-monitoring edit configmap cluster-monitoring-config
3434
+
3535
[NOTE]
3636
====
37-
If you configure cluster ID labels for metrics for the Prometheus instance that monitors user-defined projects, edit the `user-workload-monitoring-config` config map in the `openshift-user-workload-monitoring` namespace.
38-
Note that the Prometheus component is called `prometheus` in this config map and not `prometheusK8s`, which is the name used in the `cluster-monitoring-config` config map.
37+
If you configure cluster ID labels for metrics for the Prometheus instance that monitors user-defined projects, edit the `user-workload-monitoring-config` config map in the `openshift-user-workload-monitoring` namespace.
38+
Note that the Prometheus component is called `prometheus` in this config map and not `prometheusK8s`, which is the name used in the `cluster-monitoring-config` config map.
3939
====
4040

4141
. In the `writeRelabelConfigs:` section under `data/config.yaml/prometheusK8s/remoteWrite`, add cluster ID relabel configuration values:
@@ -80,10 +80,10 @@ data:
8080
action: replace <3>
8181
----
8282
<1> The system initially applies a temporary cluster ID source label named `+++__tmp_openshift_cluster_id__+++`. This temporary label gets replaced by the cluster ID label name that you specify.
83-
<2> Specify the name of the cluster ID label for metrics sent to remote write storage.
83+
<2> Specify the name of the cluster ID label for metrics sent to remote write storage.
8484
If you use a label name that already exists for a metric, that value is overwritten with the name of this cluster ID label.
8585
For the label name, do not use `+++__tmp_openshift_cluster_id__+++`. The final relabeling step removes labels that use this name.
86-
<3> The `replace` write relabel action replaces the temporary label with the target label for outgoing metrics.
86+
<3> The `replace` write relabel action replaces the temporary label with the target label for outgoing metrics.
8787
This action is the default and is applied if no action is specified.
8888

8989
. Save the file to apply the changes to the `ConfigMap` object.

0 commit comments

Comments
 (0)