diff --git a/deployment/ovn/ovn-controller-container-puppet.yaml b/deployment/ovn/ovn-controller-container-puppet.yaml
index fc178f4ff9..67ea69b6aa 100644
--- a/deployment/ovn/ovn-controller-container-puppet.yaml
+++ b/deployment/ovn/ovn-controller-container-puppet.yaml
@@ -211,6 +211,7 @@ outputs:
             ovn::controller::hostname: "%{hiera('fqdn_canonical')}"
             ovn::controller::ovn_remote_probe_interval: {get_param: OVNRemoteProbeInterval}
             ovn::controller::ovn_openflow_probe_interval: {get_param: OVNOpenflowProbeInterval}
+            ovn::controller::ovn_monitor_all: true
           - if:
               - force_config_drive
               - nova::compute::force_config_drive: true
diff --git a/releasenotes/notes/ovn-monitor-all-2fefb215c6f7166c.yaml b/releasenotes/notes/ovn-monitor-all-2fefb215c6f7166c.yaml
new file mode 100644
index 0000000000..4898359951
--- /dev/null
+++ b/releasenotes/notes/ovn-monitor-all-2fefb215c6f7166c.yaml
@@ -0,0 +1,8 @@
+---
+features:
+  - |
+    With conditional monitoring enabled in OVN, southbound ovsdb-serve
+    takes lot of time in handling the monitoring and sending the updates
+    to all its connected clients. Its takes lot of CPU. With monitor-all
+    option, all ovn-controllers do not enable conditional monitoring there
+    by reducing the load on the Southbound ovsdb-server.