You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-1Lines changed: 17 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -97,8 +97,24 @@ Logging (or tracing) can be enabled by modifying the [`mbed_app.json`](https://g
97
97
```
98
98
"mbed-trace.enable" : null,
99
99
```
100
+
By modifying that `null` to `1` and recompiling the application.
100
101
101
-
By modifying that `null` to 1 and recompiling the application. The application and client uses [`mbed-trace`](https://github.com/ARMmbed/mbed-trace) library for the logging, more fine-grained control is also possible by setting log levels (by calling `mbed_trace_config_set()`) and inclusions/exclusions (by calling `mbed_trace_include_filters_set()` or mbed_trace_exclude_filters_set()`).
102
+
Log level can be modified compile-time by defining `MBED_TRACE_MAX_LEVEL` -macro to `mbed_app.json`:
103
+
104
+
```
105
+
"target.macros_add": [
106
+
"MBED_TRACE_MAX_LEVEL=TRACE_LEVEL_INFO",
107
+
```
108
+
109
+
Default level is `TRACE_LEVEL_DEBUG`, possible values are:
110
+
*`TRACE_LEVEL_DEBUG` (largest amounts of logs)
111
+
*`TRACE_LEVEL_INFO`
112
+
*`TRACE_LEVEL_WARN` and
113
+
*`TRACE_LEVEL_ERROR` (smallest amount of logs).
114
+
115
+
Component level run-time control is also possible by setting log levels (by calling `mbed_trace_config_set()`) and inclusions/exclusions (by calling `mbed_trace_include_filters_set()` or mbed_trace_exclude_filters_set()`).
116
+
117
+
For more details, see the [`mbed-trace`](https://github.com/ARMmbed/mbed-trace) library.
0 commit comments