JEP 271: Unified GC Logging

[Tao Mao]

Regarding alternative log format, has JSON format been put on the table? It
has human and machine readability as well as extensibility (i.e., not
likely to break existing tools when new fields are added).

You can take a glance here for how JSON logs would look like in other field.

Thanks.
Tao Mao



On Thu, Sep 24, 2015 at 8:33 AM, Kirk Pepperdine <kirk at kodewerk.com> wrote:

> Hi Johann,
>
> XML is far from my favorite format. It’s unnecessarily verbose. But then,
> I also don’t care that much about “human readable” either.
>
> Kind regards,
> Kirk
>
> > On Sep 24, 2015, at 3:17 PM, Bengt Rutisson <bengt.rutisson at oracle.com>
> wrote:
> >
> >
> >
> > Hi Johann,
> >
> > Thanks for looking at the JEP!
> >
> > On 24/09/15 14:40, Johann N. Loefflmann wrote:
> >> On 09/24/2015 02:08 PM, Bengt Rutisson wrote:
> >>> and I'm happy to hear some suggestions on how to format this nicely,
> >>
> >> Why not printing out xml on demand (resp. by default if -Xloggc is set)
> ?
> >> With xml any preferred/customized output format could be generated from
> the log (e.g. plain text).
> >
> > I think this has already been discussed in the discussions around the
> JEP for the unfied logging framework "JEP 158 Unified JVM Logging". Please
> see the discussions there.
> >
> > In short I think the main point is that it is good if the logging is
> easy for tools to parse but the main intent is still that they should be
> human readable. So, XML is not a desirable format.
> >
> > Thanks,
> > Bengt
> >
> >>
> >> just my 0.02 cents,
> >> -Johann
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20150924/e1ad8948/attachment.htm>