GitHub user ramanathan1504 added a comment to the discussion: Removing `StructuredDataMessage` and all other RFC 5424 et al.
I've been looking closely at our roadmap and how this proposal to clean up legacy RFC 5424 / `StructuredDataMessage` components might intersect with other open issues. If we do proceed with removing these legacy pieces, perhaps we can consider it a great stepping stone towards the goals outlined in **Issue #1976**. Replacing these older, high-maintenance components with native support for W3C Trace Context standards (`traceId`, `spanId`, `traceFlags`) directly on `LogEvent` would give us a highly performant, modern alternative. As discussed in #1976, this would bypass the memory and GC overhead of copying `ThreadContext` maps while keeping Log4j aligned with cloud-native standards. I wanted to share this thought to see if coordinating these two topics is a direction we want to explore for Log4j 3.x. If the team agrees this is a good path forward. GitHub link: https://github.com/apache/logging-log4j2/discussions/4140#discussioncomment-17171287 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
