Read the existing Log4j2 XML configuration to confirm the JSON layout, then added a dedicated audit logger name so search events land in the existing log pipeline and can be filtered by logger name without any configuration change. Not executed.
- What worked
- A named logger was enough to segregate audit lines; no new appender or layout was needed.