The JMS appender supported it by default, so any configurations set up to
append to JMS and read them elsewhere as objects won't work by default
anymore, though that's somewhat a custom config more so than an application.

On 30 June 2017 at 08:56, Mikael Ståldal <mi...@apache.org> wrote:

> Now when we have deprecated SerializedLayout, we should attempt to get all
> known consumers of it to be changed to instead/also support JsonLayout (or
> something else if more appropriate).
>
> The Socket Server in Log4j already support JsonLayout and XmlLayout as
> well, and I have just changed it to use JsonLayout by default.
>
> I have just notified Jörn Huxhorn about Lilith.
>
> What about Chainsaw? Does it read Log4j 2 SerializedLayout? Does it
> support something else as well?
>
> What about Flume?
>
> Logback Beagle seems to be Logback specific, so we don't need to worry
> about it. https://github.com/qos-ch/logback-beagle
>
> Do we know of any other?
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to