Technically, you just need to provide a Maven module containing nothing but a `ClefLayout.json` in its `src/main/resources`. I would say the ideal place for such a Maven project would be the `clef-json` GitHub organization <https://github.com/clef-json>, since that is the closest place resembling a central spot for the community. Though if you'd look there, you see no projects but the CLEF JSON website. If you further check "Tools and resources" in the website <https://clef-json.org/#tools-and-resources>, all are GitHub projects owned by either individuals or other organizations/companies. This makes me think that CLEF is not interested in building a community and rather expects individuals/companies to come up with their 3rd party integrations by themselves.
In conclusion, do you want to ship a `ClefLayout.json`? Publish a `log4j-layout-template-json-clef` Maven project in your personal GitHub account, IMHO. Does this answer your question? On Thu, Jan 23, 2025 at 7:40 AM Jay Kataria <jaykataria1...@gmail.com> wrote: > Hi Volkan, > > What does it mean to provide an integration for a format, I guess my > curiosity is more about the documentation or steps as to how to provide an > integration. > > Do you just have to write a template for the purpose and custom resolvers? > > Regards, > Jay Katariya > > On Wed, Jan 22, 2025 at 10:36 PM Volkan Yazıcı <vol...@yazi.ci> wrote: > > > We generally (almost always?) discuss features, either in a mailing list > > thread or a PR. > > > > Log4j can neither ship integrations for every custom encoding in the > wild, > > nor it should. Good news is, Log4j is extensible > > <https://logging.apache.org/log4j/2.x/manual/extending.html> and > external > > projects (e.g., Serilog's CLEF > > <https://github.com/serilog/serilog-formatting-compact> mentioned in > #3207 > > <https://github.com/apache/logging-log4j2/issues/3207>) can easily > provide > > Log4j integrations under their own umbrella. That said, if you/users > still > > think such an extension should be part of the official Log4j > distribution, > > we can always discuss this. > > > > `*Layout.json` files you spotted under `log4j-layout-template-json` are > > JSON Template Layout's predefined event templates > > < > > > https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-templates > > > > > . > > > > > > On Thu, Jan 23, 2025 at 6:15 AM Jay Kataria <jaykataria1...@gmail.com> > > wrote: > > > > > Hi folks, > > > > > > RE: https://github.com/apache/logging-log4j2/issues/3207 > > > > > > Context: Add support to Compact Log Event Format > > > > > > Before I start the discussion here, I want to mention I am a Log4j > newbie > > > contributor, and don't know feature requests etc work, and what is a > good > > > feature vs what is not a good feature to take into account. > > > > > > I had multiple questions about this issue. > > > > > > 1. Validity of the current request, Does it sound like a good feature > to > > > have when it comes to log-4j, One customer in this case provided a need > > for > > > the purpose, do we just implement features on these request? > > > 2. What does it take to implement such stuff, I saw a bunch of layouts > > like > > > `GelfLayout.json`, `GcpLayout.json` etc. How does the processing of > these > > > files work, Is there any documentation on that or can someone provide > me > > > the links of how this plays out in action? > > > > > > > > > Regards, > > > Jay Katariya > > > Email: jaykataria1...@mail.com > > > > > >
