Skip to content

Commit

Permalink
Adding a remark that turning Warning Reporting on in Production is po…
Browse files Browse the repository at this point in the history
…intless
  • Loading branch information
VeithMetro authored Sep 14, 2023
1 parent 5718b09 commit 6924ce8
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/plugin/messaging.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 6924ce8

Please sign in to comment.