Logging CFT Weekly [2025-03-25]

[arsibo]

Participants

Saumya Rai
Gasse, Simon
Poeschel, Lars
Ahmann Philipp
Gangadhara Maddikery Raghavendra
Sievert Arvid

Agenda & Meeting Minutes

1. Give a final ok for the PR https://github.com/eclipse-score/score/pull/206/files

2. Status sync

   • S-CORE Roadmap (view)
   • Epic Epic: Logging buildable & existing tests runnable #587

3. Logging Guideline

   • docs: added log level guidelines #740
   • 7a3c6cb
   • CFT accept the proposal

4. AoB

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

• Shift to Requirements

  • Template https://eclipse-score.github.io/score/main/process/process_areas/requirements_engineering/guidance/requirements_guideline.html
  • https://eclipse-score.github.io/score/main/contribute/general/folder.html
  • PR for new structure docs: adapt folder structure #747
  • Todo: @arsibo Update FR folder structure

• BMW contribution covered functionalities

Functionality	mw::log (0.5v) offering	comments
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	-
Log severity levels	x
Log prioritization in case of resource conflicts	-
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	-	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	x	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	-
Resource consumption
Norms/Standard	x	DLT
Security	x	Files/Resources managed by lib are restricted to the userland app
ASIL	x	FFI

[rmaddikery]

Functionality	mw::log (0.5v) offering	comments
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	-
Log severity levels	x
Log prioritization in case of resource conflicts	-
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	-	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	-
Resource consumption
Norms/Standard	x	DLT
Security	x	Files/Resources managed by lib are restricted to the userland app
ASIL	x	FFI