Format logs in nested JSON

[thekamaster]

Hi

We are using logstash in our log ingestion pipeline and we found out that logs from this library are not in nested JSON format, which can cause issues in logstash processing, and also correct nested JSON formatting was highly recommanded by our elasticsearch support (as the *beats do).

An example log :
{"@timestamp":"2020-07-06T09:07:25.481Z", "log.level": "INFO", "message":"Command line argument: -Dcatalina.base=/opt/tomcat", "service.name":"tomcat","event.dataset":"catalina.out","process.thread.name":"main","log.logger":"org.apache.catalina.startup.VersionLoggerListener"}

would be :
{"@timestamp":"2020-07-06T09:07:25.481Z","log":{"level":"INFO","logger":"org.apache.catalina.startup.VersionLoggerListener"},"message":"Command line argument: -Dcatalina.base=/opt/tomcat","service":{"name":"tomcat"},"event":{"dataset":"catalina.out"},"process":{"thread":{"name":"main"}}}

Can this library output be properly nested ?
Thanks,
Alexandre

[felixbarny]

Closing as duplicate of #51 (comment).

I feel your pain. Make sure to upvote the referenced Beats issue.