-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log4j-layout-template-json Add support to Compact Log Event Format #3207
Comments
Seems interesting, I would be curious to know, how this is implemented, or looked into. I am getting familiar with the repoo, this looks like an interesting feature for people. |
@amosshi, @jaykataria1111, would you mind providing a JSON Template Layout event template for CLEF and publishing it as a part of the CLEF project with a Apache 2 License compatible license, please? If the CLEF community provides such an integration, we would be happy to point to it in the Log4j manual. |
Hi @vy , serilog/serilog-formatting-compact#69 created for CLEF side. |
@amosshi I really like your idea and suggestion. Did you get a chance to add a PR to https://github.com/clef-json/clef-json.github.io? |
Hi @TiloGit , I have connected with serilog/serilog-formatting-compact#69 - since it is a .NET library cannot used by Java application, so it is not proper to add a PR to it. So the current idea is
For now,
More info
|
@amosshi, really liked the idea of releasing the template in a dedicated artifact! 🤩
|
Warning!
It is highly recommended to discuss feature requests in the mailing lists first.
[A clear and concise description of the feature requested.]
The Problem
Currently log4j2 provides several JSON templates at:
All of current template will generate log files with long key name, which produces bigger log output.
The Request
We deliver a compact JSON format, like CLEF or similar, to make the log output smaller.
Example: CLEF format could be 47% smaller than the default EcsLayout.json.
Reference
The text was updated successfully, but these errors were encountered: