Logging
SPDX-License-Identifier: Apache-2.0
The Zephyr RTOS shall support isolation of logging from other functionality.
As a Zephyr RTOS user I want to be able to configure logging of events so the execution of logging activities does have no or only a minimal impact to the timing behaviour of my application.
The Zephyr RTOS logging shall produce logs that are capable of being post processed.
As a Zephyr RTOS user I want the logging information to be stored in a format which allows to be read possibly converted or displayed by COTS tools.
The Zephyr RTOS logging shall support formatting of log messages to enable filtering.
As a Zephyr RTOS user I want to be able my application to format texts (printf alike) into the log message.
The Zephyr RTOS logging system shall support filtering based on severity level.
As a Zephyr RTOS user I want to be able to distinguish between different severity level for my log messages (e.g. DEBUG, INFO, WARN, ERROR, PANIC).
The Zephyr RTOS shall support logging messages to multiple system resources.
As a Zephyr RTOS user I want to be able to simultaneously log to different channels which may store / redirect the information on / to different hardware (EEPROM, Flash, FRAM, UART, Ethernet, USB etc.).
The Zephyr RTOS shall support deferred logging (TODO: need more detail about the constraints and limits on what can be deferred).
As a Zephyr RTOS user I want a minimal influence of logging activities to the timing behaviour of my application. Time consuming logging threads shall be done in the background.