Update Logging option for the setting log level
In order to be able to more easily debug bmcweb related issue,
a new meson option is added to set a specific logging level
Which generates the targeted logging traces rather than all of
debug traces.
The current option -Dbmcweb-logging which can be either
disabled or enabled is changed to allow to set the log level
for the specific level traces (e.g. error or critical traces)
to be written to the journal.
-Dbmcweb-logging=<log-level>
where <log-level> can be disabled, enabled, debug, info,
warning, error, or critical.
- `disabled`: Turns off all bmcweb log traces.
- `enabled` : treated as `debug`
- Other option can be described in
[Logging Levels](DEVELOPING.md).
For an example, to enable only 'error', 'critical' log
entries, bmcweb can be built with
-Dbmcweb-logging=error
Testing:
- Verified that only the specific logs (e.g. error and
critical logs) were displayed by compiling bmcweb with the
specific bmcweb-logging level.
Change-Id: I522ca26700ea420fee1a5cf688d3e8c6661f2f55
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
diff --git a/meson_options.txt b/meson_options.txt
index 57fb8ce..0bf2c35 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -128,9 +128,13 @@
option(
'bmcweb-logging',
- type: 'feature',
+ type: 'combo',
+ choices : [ 'disabled', 'enabled', 'debug', 'info', 'warning', 'error', 'critical' ],
value: 'disabled',
- description: 'Enable output the extended debug logs'
+ description: '''Enable output the extended logging level.
+ - disabled: disable bmcweb log traces.
+ - enabled: treated as 'debug'
+ - For the other logging level option, see DEVELOPING.md.'''
)
option(