From 6924ce897aea6f86aced9a227220acfb33f4f1a8 Mon Sep 17 00:00:00 2001
From: Mateusz Daniluk <121170681+VeithMetro@users.noreply.github.com>
Date: Thu, 14 Sep 2023 11:44:40 +0200
Subject: [PATCH] Adding a remark that turning Warning Reporting on in
 Production is pointless

---
 docs/plugin/messaging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/plugin/messaging.md b/docs/plugin/messaging.md
index ffbcc6869..bb86204d7 100644
--- a/docs/plugin/messaging.md
+++ b/docs/plugin/messaging.md
@@ -172,7 +172,7 @@ Below is an example of the messaging section in the config:
 Warning Reporting enables various runtime checks for potentially erroneous conditions and can be enabled on a per-category basis. These are typically time-based - i.e. a warning will be reported if something exceeded an allowable time. Each category can also have its own configuration to tune the thresholds for triggering the warning.
 
 !!! warning
-	Warning Reporting is only available if Thunder is compiled with the `WARNING_REPORTING` option, which can be found [here](https://github.com/rdkcentral/Thunder/blob/76e08e2e5eafa12272b9080d2680091824124d9c/Source/extensions/CMakeLists.txt#L26), and is disabled by default. Note that it should not be enabled in Production, since it leads to a higher CPU and memory usage.
+	Warning Reporting is only available if Thunder is compiled with the `WARNING_REPORTING` option, which can be found [here](https://github.com/rdkcentral/Thunder/blob/76e08e2e5eafa12272b9080d2680091824124d9c/Source/extensions/CMakeLists.txt#L26), and is disabled by default. Note that it should not be enabled in Production, since it not only leads to a higher CPU and memory usage, but also it does not add any value to have it turned on in Production.
 
 ### Runtime