[
https://issues.apache.org/jira/browse/LOG4J2-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589322#comment-13589322
]
Scott Deboy edited comment on LOG4J2-155 at 2/28/13 8:09 AM:
-------------------------------------------------------------
Fix committed in svn trunk revision 1451133.
Appenders supported via advertisement: SocketAppenders, FileAppender,
RollingFileAppender
Please see the docs in the configuration page of the manual for information on
how to enable the feature.
All feedback is welcome.
Here are the attributes of the various appenders:
formatType: conversion/logfilepatternreceiver/RFC5424
port
protocol: tcp/udp
address
direction: out (could be in for a SocketHubAppender)
name
format: either a PatternLayout string or a LogFilePatternReceiver formatted
string
contentType: text/plain, text/xml, text/html or application/octet-stream
depending on the layout
dateFormat: a SimpleDateFormat formatted string
structured: false (true for RFC5424)
dtd: log4j.dtd (specified for xmllayout)
version: 1.2 (specified for xmllayout)
fileURI: URI to the file (http://, file:// or Commons-VFS supported URIs all
work with Chainsaw)
Should version be renamed to dtdversion? or applied to everything not just
xmllayout?
was (Author: sdeboy):
Fix committed in svn trunk revision 1451133.
Appenders supported via advertisement: SocketAppenders, FileAppender,
RollingFileAppender
Please see the docs in the configuration page of the manual for information on
how to enable the feature.
All feedback is welcome.
Here are the attributes of the various appenders:
formatType: conversion/logfilepatternreceiver/RFC5424
port
protocol: tcp/udp
address
direction: out (could be in for a SocketHubAppender)
name
format: either a PatternLayout string or a LogFilePatternReceiver formatted
string
contentType: text/plain, text/xml, text/html or application/octet-stream
depending on the layout
dateFormat: a SimpleDateFormat formatted string
structured: false (true for RFC5424)
dtd: log4j.dtd (specified for xmllayout)
version: 1.2 (specified for xmllayout)
Should version be renamed to dtdversion? or applied to everything not just
xmllayout?
> add getFormat to Layout
> -----------------------
>
> Key: LOG4J2-155
> URL: https://issues.apache.org/jira/browse/LOG4J2-155
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Scott Deboy
> Attachments: log4j2-155-feb21-rev1.patch,
> log4j2-155-feb24-rev1.patch, log4j2-155-jan22-rev1.patch,
> log4j2-155-jan23-rev1.patch
>
>
> I was looking at an old rev - getContentType is now exposed - thanks!
> Now if we could add a 'getFormat':
> It would be useful to expose information about a Layout's format.
> If the content type is text/plain, exposing the layout format as a conversion
> pattern would work fine.
> If the content type is text/html or text/xml we could expose something else
> (or null).
> My primary interest is adding the ability to 'discover' the file-based
> logging configurations in order to support them via Chainsaw and multicast
> DNS.
> If all Layouts supporting text/plain content types exposed their format as a
> conversion pattern, and the file-based appenders (optionally) provided the
> ability to advertise their configuration, the files could be remotely tailed
> without the far endpoint even knowing anything about the file configuration.
> For an example, see how multicast appenders are exposed via
> zeroconf/multicast dns in log4j 1.x in activateOptions - something very
> similar could be done with contenttype and format properties in a
> fileappender with a layout.
> if (advertiseViaMulticastDNS) {
> Map properties = new HashMap();
> properties.put("multicastAddress", remoteHost);
> zeroConf = new ZeroConfSupport(ZONE, port, getName(), properties);
> zeroConf.advertise();
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
