As a committer, yes, feel free to use the dev field. The due-to field
is used for contributions from outside the project.

On Thu, Jul 1, 2021 at 4:48 PM Raman Gupta <[email protected]> wrote:
>
> FYI:
>
> https://issues.apache.org/jira/browse/LOG4J2-3116
>
> https://github.com/apache/logging-log4j2/pull/543
>
> One administrative note -- as I am a committer (although thus far I have
> only committed to the log4j2 kotlin repo) should I do dev="rgupta" instead
> of adding myself in due-to?
>
> Some technical notes -- some of the functionality could be more efficient
> with some changes to the resolvers, to avoid delegating so many of the
> fields to the pattern resolver. Specifically:
>
> 1) the level resolver could be enhanced with a label mapping function,
> 2) the message resolver could optionally output stack trace as well, and
> 3) a serial number resolver could be added.
>
> However, in my opinion we should commit the basic functionality first, and
> deal with those sorts of optimizations later.
>
> Regards,
> Raman
>
>
>
> On Thu, Jul 1, 2021 at 3:06 PM Volkan Yazıcı <[email protected]>
> wrote:
>
> > That is a great idea Raman! Would you mind creating a PR along with a Jira
> > ticket, please? I would appreciate if you can take the following into
> > account:
> >
> >    - Target release-2.x branch for the PR
> >    - Prefix the PR title with the Jira ticket id
> >    - Update json-template-layout.adoc.vm (See the "predefined event
> >    templates" paragraph there.)
> >    - Update changes.xml (... dev="vy" ... due-to="Raman Gupta")
> >    - Put the file to
> >    log4j-layout-template-json/src/main/resources/GcpLoggingLayout.json
> >
> > Kind regards.
> >
> > On Thu, Jul 1, 2021 at 12:09 AM Raman Gupta <[email protected]> wrote:
> >
> > > I was thinking about contributing a JsonTemplateLayout for the structured
> > > logging format expected by Google Cloud Logging [1].
> > >
> > > This is what I've come up with so far: any comments are welcome:
> > > https://gist.github.com/rocketraman/824ca9527bb8c7226d40db2b4d78efa7.
> > >
> > > [1] https://cloud.google.com/logging/docs/structured-logging
> > >
> > > Regards,
> > > Raman
> > >
> > >
> >

Reply via email to