Configuration guide of structured logging for Kyuubi server #6861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
It's a common use case that the user may want to send the service logs in a structured format to Kafka and then collect them into centralized log services for further analysis, fortunately, the Kyuubi used logging frameworks Log4j2 has built-in KafkaAppender and JSON Template Layout, thus the goal could be achieved by just a few configurations.
To simplify the user setup steps, this PR adds
log4j-layout-template-json-<version>.jar
into Kyuubi binary tarball.PS: I also plan to support sending engine bootstrap process(e.g.
spark-submit
) logs into Kafka with specific labels in the follow-up PRs.How was this patch tested?
Manually test.
Configuration in
$KYUUBI_HOME/conf/log4j2.xml
Check that Kafka receives the expected structured logging message in the Elastic Common Schema(ECS) layout.

Was this patch authored or co-authored using generative AI tooling?
No