vy commented on code in PR #2665: URL: https://github.com/apache/logging-log4j2/pull/2665#discussion_r1642496185
########## src/site/antora/modules/ROOT/pages/manual/eventlogging.adoc: ########## @@ -17,236 +17,35 @@ = Event Logger -The `EventLogger` class provides a mechanism for logging significant events -in an application using structured data. This approach is beneficial for -tracking user actions, monitoring system behavior, and debugging issues. +link:../javadoc/log4j-api/org/apache/logging/log4j/EventLogger.html[`EventLogger`] is a convenience to log xref:manual/messages.adoc#StructuredDataMessage[`StructuredDataMessage`]s, which format their content in a way compliant with https://datatracker.ietf.org/doc/html/rfc5424#section-6[the Syslog message format described in RFC 5424]. Review Comment: Fixed in 9b576968103f5f25acfd530e09ac5218cb92a4c8. ########## src/site/antora/modules/ROOT/pages/manual/layouts.adoc: ########## @@ -29,10 +29,20 @@ This page will try to answer following questions: This section introduces you to some common concerns shared by almost all <<collection,predefined layouts>> that you need to be aware of while using them. +[#structured-logging] +=== Structured logging + +Log4j strives to provide top of the class support for *structured logging*. +To create an end-to-end experience, it provides several xref:manual/messages.adoc#collection-structured[structured message types] along with layouts supporting structured logging. + +include::partial$manual/structured-logging.adoc[] Review Comment: Fixed in e6f2cd98126de18f4db9e6e8b75439dca222f27f. -- 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]
