diff --git a/install_config/monitoring/configuring-etcd-monitoring.adoc b/install_config/monitoring/configuring-etcd-monitoring.adoc
index b1860ddd0fb9..5c2a29467e8b 100644
--- a/install_config/monitoring/configuring-etcd-monitoring.adoc
+++ b/install_config/monitoring/configuring-etcd-monitoring.adoc
@@ -7,7 +7,7 @@
 
 If the `etcd` service does not run correctly, successful operation of the whole {product-title} cluster is in danger. Therefore, it is reasonable to configure monitoring of `etcd`.
 
-Follow these steps to configure `etcd` monitoring:
+To enable the `etcd` monitoring:
 
 .Procedure
 
@@ -27,68 +27,20 @@ node-exporter-b2mrp                            2/2       Running             0
 node-exporter-fd52p                            2/2       Running             0          33m
 node-exporter-hfqgv                            2/2       Running             0          33m
 prometheus-k8s-0                               4/4       Running             1          35m
-prometheus-k8s-1                               0/4       ContainerCreating   0          21s
+prometheus-k8s-1                               4/4       Runinng             0          35m
 prometheus-operator-6c9fddd47f-9jfgk           1/1       Running             0          36m
 ----
 
-. Open the configuration file for the cluster monitoring stack:
+. Set this variable to `true` in the Ansible inventory file:
 +
-----
-$ oc -n openshift-monitoring edit configmap cluster-monitoring-config
-----
-
-. Under `config.yaml: |+`, add the `etcd` section.
-
-.. If you run `etcd` in static pods on your master nodes, you can specify the `etcd` nodes using the selector:
-+
-----
-...
-data:
-  config.yaml: |+
-    ...
-    etcd:
-      targets:
-        selector:
-          openshift.io/component: etcd
-          openshift.io/control-plane: "true"
-----
+`openshift_cluster_monitoring_operator_etcd_enabled`
 
-.. If you run `etcd` on separate hosts, you need to specify the nodes using IP addresses:
+. If you run `etcd` on separate hosts, set this variable in the Ansible inventory file to specify the nodes using IP addresses:
 +
-----
-...
-data:
-  config.yaml: |+
-    ...
-    etcd:
-      targets:
-       ips:
-       - "127.0.0.1"
-       - "127.0.0.2"
-       - "127.0.0.3"
-----
+`openshift_cluster_monitoring_operator_etcd_hosts`
 +
 If the IP addresses for `etcd` nodes change, you must update this list.
 
-. Verify that the `etcd` service monitor is now running:
-+
-----
-$ oc -n openshift-monitoring get servicemonitor
-NAME                  AGE
-alertmanager          35m
-etcd                  1m <1>
-kube-apiserver        36m
-kube-controllers      36m
-kube-state-metrics    34m
-kubelet               36m
-node-exporter         34m
-prometheus            36m
-prometheus-operator   37m
-----
-<1> The `etcd` service monitor.
-+
-It might take up to a minute for the `etcd` service monitor to start.
-
 . Now you can navigate to the web interface to see more information about the status of `etcd` monitoring.
 
 .. To get the URL, run:
diff --git a/install_config/monitoring/configuring-openshift-cluster-monitoring.adoc b/install_config/monitoring/configuring-openshift-cluster-monitoring.adoc
index 0ff43bdd45d0..7f65fb5bbbe4 100644
--- a/install_config/monitoring/configuring-openshift-cluster-monitoring.adoc
+++ b/install_config/monitoring/configuring-openshift-cluster-monitoring.adoc
@@ -40,6 +40,12 @@ The {product-title} Ansible `openshift_cluster_monitoring_operator` role configu
 |`openshift_cluster_monitoring_operator_alertmanager_storage_class_name`
 | If you enabled the `openshift_cluster_monitoring_operator_alertmanager_storage_enabled` option, set a specific StorageClass to ensure that pods are configured to use the `PVC` with that `storageclass`. Defaults to `none`, which applies the default storage class name.
 
+|`openshift_cluster_monitoring_operator_etcd_enabled`
+| Enable `etcd` monitoring. This variable is set to `false` by default.
+
+|`openshift_cluster_monitoring_operator_etcd_hosts`
+| The list of IP addresses of the `etcd` hosts when `etcd` runs on separate nodes.
+
 |===
 
 [[monitoring-prerequisites]]