ppkarwasz commented on issue #1813: URL: https://github.com/apache/logging-log4j2/issues/1813#issuecomment-1732406834
> I can also see enhancing MapMessage to add the message as a separate attribute instead of relying on the name of the key. In that case the third option would be unneccesary as the value of the message attribute would always be logged separately at the end if it is non-null. I think this would be the best options. As far as I can understand the new SLF4J features allow to create messages similar to RFC5424 (minus the SD-ID) with a message and a map of key-values, so it should be similar to the `StructuredDataMessage`. Although I am not sure what we should do if the user provides a message format, some parameters and a set of key/value pairs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
