Quick heads-up everyone. So since last email, the proposal got accepted as
JEP-304.
After a discussion yesterday with Tyler, we discussed a small adjustment to
make JSON parsing and evolution more straightforward, making the
`exception` field an object instead of a string as it was currently.
Seems reasonable.
The implementation separates JSON records with a newline. This is not
apparent from the JEP; it would be nice to mention it, so that readers
do not wonder whether you are using some kind of streaming JSON parser
(which is unnecessary when each line is a well-formed JSON
Hello everyone,
So as a followup on the recent discussions around telemetry logging for
Essentials, I've drafted a JEP on this matter I would love to get feedback
on:
https://github.com/batmat/jep/tree/JENKINS-49805/jep/
Thanks!
-- Baptiste
--
You received this message because you are
