You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2023/12/01 23:36:00 UTC

[jira] [Resolved] (LOG4J2-1871) Add an Avro layout for extensible binary encoding

     [ https://issues.apache.org/jira/browse/LOG4J2-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker resolved LOG4J2-1871.
---------------------------------
    Resolution: Won't Fix

I'm closing this as we've discussed the idea behind binary layouts before, and the consensus was that it was fairly pointless to support any binary format that isn't already supported by various log tooling in the first place. The closest we may come to this would be related to OpenTelemetry, but that looks like it uses gRPC, not Avro.

> Add an Avro layout for extensible binary encoding
> -------------------------------------------------
>
>                 Key: LOG4J2-1871
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1871
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Layouts
>            Reporter: Matt Sicker
>            Priority: Major
>
> Similar in style to the JSON layout (and other related dynamic layouts), a new layout based on [Apache Avro|https://avro.apache.org/docs/current/] would be a good choice for simple binary layouts. Avro also provides adapters for Apache Thrift and Protobuf, so this library makes sense as a good choice for the most extensible binary layout. This also opens up the ability to create a socket appender or similar using the Avro IPC classes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)