FYI, I think most folks just use pattern layout, which probably makes VFSLogFilePatternReceiver the most commonly used receiver. Since it's VFS, anything accessible over SSH is retrievable and can be live-tailed.
Also, Chainsaw V2 can pull in logs generated by Log4j2 if you configure an Advertiser - it uses VFSLogFilePatternReceiver, which assumes your source can be pulled via one of VFS's supported sources (file:// or sftp:// are the most common). I use VFSLogFilePatternReceiver in my cloud configs to remotely tail logs from multiple hosts and combine those logs into a single view in Chainsaw. Scott On 10/16/17, Matt Sicker <boa...@gmail.com> wrote: > On 16 October 2017 at 14:19, Mikael Ståldal <mi...@apache.org> wrote: > >> I think that adding support for Log4j 2's JsonLayout should be top >> priority when we have figured out how to build, release and distribute >> it. >> It should be fairly easy since we can use the new JsonLogEventParser in >> log4j-core. >> > > Agreed. Moving away from serialized layouts and having first class support > for any type of safer serialized layout (in this case, the existing json > layout) should be emphasized. > > -- > Matt Sicker <boa...@gmail.com> >
