Log Events Sent in Batch Mode are not Recognized as Individual Events by Loggly about logback-extensions

[MusikPolice]

On further inspection of the POST request content body in a hex editor, I can see that there is no newline character between the JSON log event objects.

For example, given the two log event objects {"foo": "bar"}{"hello": "world"} in ASCII, the associated hex that is generated by the encoder would be 7b 22 66 6f 6f 22 3a 20 22 62 61 72 22 7d 7b 22 68 65 6c 6c 6f 22 3a 20 22 77 6f 72 6c 64 22 7d.

Note that in the example above, the { character is denoted by the hex code 7b and the } character is denoted by the hex code 7d. You can see that the 14th and 15th characters in the hex string are 7d and 7b respectively, indicating that there is no newline character being printed between them.

This is the bug that is causing Loggly to interpret all JSON events as a single event.

[MusikPolice]

I got a bulk request to work with a REST debugging tool. It looks like the hex character that Loggly expects in between each log entry JSON object is 0A, which http://www.asciitable.com/ refers to as NL line feed, new Line.

[MusikPolice]

I have created pull request #21 to resolve this issue. Please let me know if there is anything further that is required before this patch can be accepted into the mainline.

[tony19]

Fixed in 56de824

[pathikrit]

Can we release this as 0.1.3 to maven? I believe Maven still has the old buggy 0.1.2 only: http://mvnrepository.com/artifact/org.logback-extensions/logback-ext-loggly

[tony19]

@pathikrit 0.1.3 should be available now via Maven Central. The search interface may take a few hours to index the new version.