[
https://issues.apache.org/jira/browse/LOG4J2-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925616#comment-13925616
]
Mark Paluch commented on LOG4J2-428:
------------------------------------
GELF isn't just a simple JSON data structure. GELF supports compression and
needs message chunking. GELF uses a set of own field names which are required
by the protocol itself and prefixes custom fiedls. This would result in an
customized JSONLayout. The appender it self needs to split large messages (>
8192 bytes) into multiple GELF message chunks (with message number, not only a
simple partitioning of the Layout byte array). Therefore I see it necessary to
have a custom appender. I guess, that there is perhaps any way to customize
log4j/log4j2 with lots of settings to make GELF work (in some way) but it's way
to complex.
It's up to you whether you integrate the code as component package or a sub
project. It was easier to me to submit the code as subproject.
> Integration of GELF Appender
> ----------------------------
>
> Key: LOG4J2-428
> URL: https://issues.apache.org/jira/browse/LOG4J2-428
> Project: Log4j 2
> Issue Type: Wish
> Components: Appenders
> Affects Versions: 2.0
> Reporter: Mark Paluch
> Attachments: log4j-gelf.patch, log4j-gelf.zip
>
>
> I'd like to propose the integration of a GELF (Graylog Extended Log Format)
> Appender into log4j2 on a basis like the flume-ng Appender.
> See https://github.com/mp911de/logstash-gelf for the code.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
