Logging CFT Weekly [2025-12-02]

[arsibo]

Participants

Maciej Kaszynski
Jianjun
Ragha
Alekhya
Nils Hoppe
Rahul
Pawel
SaumyaR

Agenda & Meeting Minutes

1. Pawel will send a PR for Component architecture and detailed design for Rust front_end @ all please review until next week

• Pawel will send a PR for the first part of the implementation @ all please review

2. Mapping Feature to component requirements (C++ front_end)
3. Design Diagramms

• @ all please add sub tickets to [Story] Create Design diagrams #1863 for your self
  • pick up some puml diagrams, check the consistency to baseline code and correct if needed

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

[hoppe-and-dreams]

That's what I noted down for the mapping of requirements.
Obviously ? means not clear, needs discussion/revisiting.
The points have been discussed in the CFT but are still only my personal first thoughts on the topic and open for re-evalaution.

ID Excel	ID Feature Req
578990	?
29118440	?
29118765	?
1632647	?
1573751	?
1573764	feat_req__logging__config_log_filter
1633539	feat_req__logging__compat_dlt
26320994	?
26319707	?
1633144	feat_req__logging__compat_dlt
1633236	feat_req__logging__compat_dlt
1633238	Drop Candidate
1633254	feat_req__logging__filtering_log_levels
1016729	feat_req__logging__config_permissions
8017664	Need addition in FR if we want to have it
8017693	as above
1633294	feat_req__logging__config_entity_id
1633316	feat_req__logging__config_log_filter ; feat_req__logging__filtering_log_levels ; feat_req__logging__filtering_entity_id
1634075	feat_req__logging__config_fallback
7263552	feat_req__logging__config_fallback
7263547	feat_req__logging__config_fallback
7263537	feat_req__logging__config_fallback
7263548	feat_req__logging__config_fallback
861534	From general (Safety) rules
861550	From general (Safety) rules
861578	Safety rules
1016724	From general (Safety) rules
1016719	From general (Safety) rules
861827	From general (Safety) rules