Elasic.co got it wrong in that blog post. The problem is not
SockerAppender, the problem is SerializedLayout.
Maybe people were confusing the two, since SerializedLayout used to be
default layout for SockerAppender. But it has always been possible to
configure SockerAppender to use another layout. And since Log4j 2.9.0,
SerializedLayout is deprecated and no longer default in any appender.
You can use SockerAppender with JsonLayout for sending log events to
Logstash.
On 2017-10-24 08:25, itsg...@gmail.com wrote:
Thanks. We have a situation where we have a thick client application (Java
Swing) and we want the client side logs to be pushed to server side so that
we can use for analysis. Socketappender is one option but looks like there
are plan to depricate socket appenders because of security issues. Please
refer to below
https://www.elastic.co/blog/log4j-input-logstash
--
Sent from: http://apache-logging.6191.n7.nabble.com/Log4j-Users-f4.html
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
