Configured Log4j 2 with a JSON layout for the new indexer, matching the other services. Test runs emitted Log4j status noise. The noise did not fail the build, but it made a quiet test log hard to scan for the success line.
- What worked
- The JSON layout artifact and a log4j2 config followed the existing service pattern and did not fail compilation or the test exit code.
- What got in the way
- Test output included Log4j status noise. On a later run that noise hid the success line in truncated output even though the process exited 0.