Logging CFT Weekly [2025-09-30]

[arsibo]

Participants

@darkwisebear
@Saumya-R
@arsibo
@4og
@sankurm
@calbryan1

Agenda & Meeting Minutes

1. discussion about rust api
   Proposal: Extend log crate with contextual, typed, and fatal-level logging rust-lang/log#700
   why we have not used an existing solution https://docs.rs/log/latest/log/?
   =>Task: generate an ADR (first version)

2. Status Tasks

   • backlog refinement
     • Feature Architecture => Arvid
     • Convert from starUML to Plant UML with Github Copilot & Claude 4.0
       => @sankurm: Please check on witch diagrams BMW is still working (Slack/Comment)
       Move diagrams for mw/log to incubation repo inc_mw_log#7
       • describe acceptance criteria in the review tasks

3. AoB

   • https://sdvworkinggroup.slack.com/archives/C089XP2PGQZ
   • Json schema for logging?
     • @rmaddikery: Please check if we use a json schema for logging configuration .

Next meeting

• status rust api; decision about fork or not fork for quick fix
• @rmaddikery: Please prepare a list of high level task description about the planed BMW contribution. Goal is the alignment of S-Core and BMW planning
• Json schema

[rmaddikery]

@arsibo

• There is NO json schema for logging configuration. Supports JSON Standard RFC-8259
• High-level task description about the planed BMW contribution
  • Separate logging repo for logging backends - file, system, remote. Ref: https://github.com/eclipse-score/logging
  • GCC toolchain for compiling and building bazel targets.
  • Third party deps for tooling
  • mw::log split frontend and backend: frontend stays in baselibs and backends move to logging repo.
  • Remote backed as datrouter - Ref: Epic: S-CORE v0.5 Logging Feature Complete (Epic: S-CORE v0.5 Logging Feature Complete #633)
    • Features: https://github.com/orgs/eclipse-score/discussions/770#discussioncomment-12613597
    • Third party deps for datarouter daemon