Logging CFT Weekly [2025-09-02]

[pahmann]

Participants

Agenda & Meeting Minutes

1. Status Tasks

   • Effort estimation (see last meeting notes: https://github.com/orgs/eclipse-score/discussions/1625)

2. AoB

   • https://sdvworkinggroup.slack.com/archives/C089XP2PGQZ

[pahmann]

Past ToDos:

• ToDo: Estimation for verbose RUST API
• ToDo: Discuss baselib c++ and baselib Rust dependency handling. e.g. Rust API Facade for logging=> baselib Rust depends on baselib c++ for logging

Overview from last meeting

Functionality	mw::log (0.5v) offering	comments	effort to close the gap
Timestamping	x
local timestamp for each log entry	x
original timestamp for routed log entries	x
timestamp synchronization for log entries coming from different logging nodes	-	ToDo: Understand the Req & define Use cases.	?
Log severity levels	x
Log prioritization in case of resource conflicts	-	- reccources    - CPU    - Memory    -network (message drops) - assumtion the datarouter shall handle this functionality. This means an intreface between the Execution manger  like FEO,.. Is required. - The degradation concept can be configerd in the datarouter.
logging of early startup events	x	depends on backend
Log filtering
Support application and context identifier like in DLT	x
Filtering by log levels for components and application level	x
logs filtering by logging entity ID (e.g., ECU ID, Application ID, Context ID such as in DLT)	x
logs filtering by log level (Info, warn, debug, etc)	x
logs filtering by app_id and context_id	x
message loss detection	x	dropped message stats
Context specific log level activation at runtime	-
Log Sources	x
Log Sinks	x
Log Sink - Console	x
Log Sink - File	x
Log Sink - Remote	x	DLT backend
Logs shall appear on stdout when running unit tests	x
Configuration	x
Log level	x
Log Sinks	x
Buffer size	x
Storage size	-
Permission setting	-
Log filter	x
Logging entity ID (e.g., ECU ID, Application ID, Context ID such as in DLT)	x
On-demand functionality (e.g., enable / disable the log storage)	-
Provide fallback configs. E.g.: App, System-wide	x
Possibility to provide an extension for custom types	x
TRACE	-	Raw C++ structs
Error handling	x
reboot/reset	-
On logging errors, the framework should continue if recoverable; otherwise, deactivate logging a fatal and set an error state reported on shutdown.	x
The user application should not be affected by logging framework errors.	x	FFI
Context	x
POSIX	x
Supported programming languages: C++	x
Supported programming languages: Rust	-	Important topic for 0.5 due to the dependency to FEO	- verbose = - non-verbose
Resource consumption
Norms/Standard	x	DLT
Security	x	Files/Resources managed by lib are restricted to the userland app
ASIL	x	FFI

[pahmann]

Participants:

@pawelrutkaq
@pahmann

Topics added:

• PR: Enabler for rust log to be used in S-CORE inc_mw_log#6
  • Need to move forward with this PR forward, requiring review from S-Core members.
  • Internal review from Qorix is done already, so need additional feedback from other people
  • Reviewer from Rust users and from Logging members would be useful.
  • @arsibo will only be able to review after his return mid of September.
  • Pinged the slack channel for their review. https://sdvworkinggroup.slack.com/archives/C089XP2PGQZ/p1756804625350189