At my previous work, we first used Log4j 2 and Graylog, and Logstash in between. But then I developed GelfLayout (now part of log4j-core) and we could configure Log4j 2 to send log events directly to Graylog, and Logstash became unnecessary.
Can we do something similar with ELK (so that it become just "E-K")? Can we develop an ElasticSearchAppender for Log4j 2? On Thu, Nov 19, 2015 at 1:07 PM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > Is is even necessary to add Logstash to the mix? I think that Log4j 2 > should be able to whatever is necessary by itself without either Flume or > Logstash. > > > On Wed, Nov 18, 2015 at 10:56 PM, David KOCH <dk...@ezakus.com> wrote: > >> We use log4j2's SyslogAppender and a logstash UDP input source, works ok >> for us, no need to add Flume to the mix. >> >> /David >> >> On 18 November 2015 at 22:35, Matt Sicker <boa...@gmail.com> wrote: >> >> > Any experience with this? I was thinking of using Flume and the Flume >> > appender to route all my log messages to an ELK stack, but I was >> wondering >> > if there were other ways of doing this. >> > >> > -- >> > Matt Sicker <boa...@gmail.com> >> > >> > > > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > mikael.stal...@magine.com > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
