JSON columnizer does not work properly

[DoubleDHZ]

See attachment for sample JSON.

sample.log

Lines 1 & 3 are processed & displayed properly.
Line 2 isn't processed at all and is put as a whole into the very last column ("SpanId" in that case)

Line 3 is a copy of Line 2 with the properties level, Classname, Methodname, Thread, SourceLineNumber & CorrelationId removed.

Found in LogExpert v1.20.0

[Hirogen]

When I open the file with notepad++ I get a json error, you sure the log is correct?

It seems like, the 2nd line can not be parsed as json, so something is up with that one

[DoubleDHZ]

The log as a whole is not a well-formed JSON, but only each line on its own is.

[Hirogen]

the columnizer parses line for line, and gets an parse exception with line 2 so something is up with line 2

I'll have closer look when I'm back from my holidays