Lines Matching refs:logs
37 Kconfig options (see :ref:`logging_kconfig`) logs can be gradually removed from
38 compilation to reduce image size and execution time when logs are not needed.
39 During compilation logs can be filtered out on module basis and severity level.
69 to globally limit logs by providing maximal severity level present in the
145 :kconfig:option:`CONFIG_LOG_FRONTEND`: Direct logs to a custom frontend.
249 across the system enabling logs will lead to flooding. The logger provides the tools
340 If logs are processed from a thread (user or internal) then it is possible to enable
356 that moment all logs are processed in a blocking way.
462 logs to limit dropping.
477 time filtering, binary footprint is increased because logs are compiled in.
501 In some cases, logs need to be redirected at the macro level. For these cases,
531 as logs are presented on independent outputs.
549 have backends that output logs to the user. It has a cross-domain backend either to
551 * The *root domain* has one or multiple links and a backend that outputs logs
624 As such, to filter logs in multiple domains, each source requires a runtime
662 to dynamically change filtering of a module logs for given backend. Module is