Requirements#

Timestamping - Local Timestamp
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support local timestamps for each log entry.

Timestamping - Original Timestamp
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support original timestamps for routed log entries.

Timestamping - Timestamp Synchronization
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support timestamp synchronization for log entries coming from different logging nodes.

Log Severity Levels
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support a log level for each log entry.

Log Prioritization
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall prioritize logs in case of resource conflicts to ensure critical logs are not lost.

Logging of Early Startup Events
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support logging of early startup events to capture critical initialization information.

Log entity Identifier
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support logging entity identifiers for each log entry.

Log Filtering - Log Levels
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support filtering by log levels.

Log Filtering - Logging Entity ID
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support filtering by logging entity identifiers.

Message Loss Detection - Detection and Reporting
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall detect and report any message loss.

Message Loss Detection - Graceful Handling
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall provide mechanisms to handle message loss gracefully.

Additional Information: e.g. buffering or prioritizing critical messages

Context-Specific Log Level Activation
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow context-specific log level activation at runtime to enable fine-grained control over logging behavior.

Log Sources - User Application
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support user application as log source.

Log Sources - Component and Platform
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support component features and :term:` platform` as log sources.

Log Sinks - Console
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support console as a log sink.

Log Sinks - Local File System
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support local file system as log sink.

Log Sinks - Cloud Native Drive
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support cloud-native drives via network as log sinks.

Log Sinks - Network
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support network channels, including a second dedicated Ethernet channel, as log sinks.

Log Sinks - Stdout for Unit Tests
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall ensure logs appear on stdout when running unit tests.

Previous boot logging
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support logging of data to memory which survives a reboot cycle.

Configuration - Log Level
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support configuration of log levels.

Log Sinks - Storage Device
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support configuration of the log storage device.

Log Sinks - multiple Storage Device
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support multiple log storage devices.

Log Sinks - Storage Strategy
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support configurable log storage strategy.

Configuration - Buffer Size
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow configuration of internal buffers sizes.

Configuration - Storage Size
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow configuration of storage size per log file.

Configuration - Permission Settings
status: valid
security: YES
safety: QM
reqtype: Functional

The logging framework shall allow configuration of permission settings for log access.

Configuration - Log Filter
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow configuration of log filters.

Configuration - Logging Entity ID
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow configuration of logging entity IDs.

Configuration - On-Demand Functionality
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall support on-demand functionality, such as enabling or disabling log storage.

Configuration - Fallback Configurations
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall provide fallback configurations, such as application-wide or system-wide defaults.

Configuration - Custom Types Extension
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall allow extensions for custom log types.

Error Handling - Recoverable Errors
status: valid
security: NO
safety: QM
reqtype: Functional

In case of recoverable error, the logging framework shall continue the current operations.

Error Handling - Non-Recoverable Errors
status: valid
security: NO
safety: QM
reqtype: Functional

In case of non-recoverable error, the logging framework shall deactivate silently and set an error state reported on shutdown.

Error Handling - Application Isolation
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall ensure that user applications are not affected by logging framework errors.

Compatibility - Supported Operating Systems
status: valid
security: NO
safety: QM
reqtype: Interface

The logging framework shall support QNX and Linux operating systems (encapsulated via OSAL).

Compatibility - Supported Programming Languages
status: valid
security: NO
safety: QM

The logging framework shall support C++, Rust, and Python programming languages.

Resource Consumption - Storage
status: valid
security: NO
safety: QM
reqtype: Non-Functional

The logging framework shall minimize storage resource consumption.

Resource Consumption - Communication Channel
status: valid
security: NO
safety: QM
reqtype: Non-Functional

The logging framework shall minimize communication channel resource consumption.

Resource Consumption - Runtime Resources
status: valid
security: NO
safety: QM
reqtype: Non-Functional

The logging framework shall minimize runtime resource consumption.

Resource Consumption - Performance Impact
status: valid
security: NO
safety: QM
reqtype: Functional

The logging framework shall have low impact on overall system performance.

Quality of Service - Message Handling
status: valid
security: NO
safety: QM
reqtype: Non-Functional

The logging framework shall provide:term:` QoS` for handling overflows or dropping log messages.

Compatibility - DLT Protocol
status: valid
security: NO
safety: QM

The logging framework shall be DLT compatible.

Additional Information: support for DLT message format, sending and receiving DLT messages, and integration with existing DLT tools and infrastructure.

Security - Log File Access
status: valid
security: YES
safety: QM

The logging framework shall ensure that only authorized users can access log files.

Safety - ASIL Level Support
status: valid
security: NO
safety: ASIL_B
reqtype: Non-Functional

The logging framework shall support the ASIL level of the user function to ensure compliance with the safety requirements of the application.

Additional Information: Freedom from interfernce must be guaranteed with regard to the calling components.

Safety - System Classification
status: valid
security: NO
safety: QM
reqtype: Non-Functional

The logging framework shall be classified according to the overall system’s safety concept if logging information is part of the verification strategy.