[jira] [Updated] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-338: --- Attachment: documentation_notes.patch > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Fix For: 2.0-beta9 > > Attachments: add_TLSSyslogAppender.zip, documentation_notes.patch > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Commented] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760149#comment-13760149 ] Tibor Benke commented on LOG4J2-338: Thank you! I added some notes to the documentation and I'm going to attach the patch. > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Fix For: 2.0-beta9 > > Attachments: add_TLSSyslogAppender.zip, documentation_notes.patch > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Commented] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758847#comment-13758847 ] Tibor Benke commented on LOG4J2-355: The eventPrefix was introduced by Ralph in this commit: http://mail-archives.apache.org/mod_mbox/logging-commits/201304.mbox/%3c20130418224222.4b0a62388...@eris.apache.org%3E Ralph, do you think it is still needed? In that case I'm going to make a patch. And I'm going to write some docs about the LoggerFields in the RFC5424Layout's site documentation after we made a decision. > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Fix For: 2.0-beta9 > > Attachments: add_multime_SD_ELEMENT_support.diff, > eventPrefix_behaviour_demo_testcase.patch, LOG4J2-355_v2.patch, > LOG4J2-355_v3.patch, LOG4J2-355_v4.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Updated] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-355: --- Attachment: eventPrefix_behaviour_demo_testcase.patch > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Fix For: 2.0-beta9 > > Attachments: add_multime_SD_ELEMENT_support.diff, > eventPrefix_behaviour_demo_testcase.patch, LOG4J2-355_v2.patch, > LOG4J2-355_v3.patch, LOG4J2-355_v4.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757865#comment-13757865 ] Tibor Benke commented on LOG4J2-355: Hi Gary, I think, we won't need anymore the getId(StructuredDataId) method, so you can remove it. It's functionality partially implemented in the LoggerFields class. On the other hand, as far as I can see we used the eventPrefix to mark all key-value pairs in a StructuredDataMessage. I forgot to reimplement this during the partial refactor, but after all, I think there is a better solution. Now, you can create a new SD-Element from a StructuredDataMessage, which is IMHO a more elegant way to "prefix" our key-value pairs. But, it's easy to use the eventPrefix again. What do you think about it? P.S: for demonstrating the behaviour what I described above, I'm going to upload a new testcase to RFC5424LayoutTest.java. Best wishes, Tibor > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Fix For: 2.0-beta9 > > Attachments: add_multime_SD_ELEMENT_support.diff, > LOG4J2-355_v2.patch, LOG4J2-355_v3.patch, LOG4J2-355_v4.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757727#comment-13757727 ] Tibor Benke commented on LOG4J2-338: Ralph, can I help you in anything? I want to wait until LOG4J2-355 will be applied, because it will broke again this patch and I don't want to recreate it too many times. > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Attachments: add_TLSSyslogAppender.zip > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Commented] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757717#comment-13757717
]
Tibor Benke commented on LOG4J2-374:
It's my pleasure :)
I verified the modifications.
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Reporter: Tibor Benke
> Fix For: 2.0-beta9
>
> Attachments: LOG4J2-374.patch, LOG4J2-374_v2.patch
>
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Closed] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Benke closed LOG4J2-374.
--
It has been verified and complete.
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Reporter: Tibor Benke
> Fix For: 2.0-beta9
>
> Attachments: LOG4J2-374.patch, LOG4J2-374_v2.patch
>
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Updated] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-355: --- Attachment: LOG4J2-355_v4.patch I solved the bug and attached the new (and hopefully last) patch (LOG4J2-355_v4.patch). > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff, > LOG4J2-355_v2.patch, LOG4J2-355_v3.patch, LOG4J2-355_v4.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757690#comment-13757690 ] Tibor Benke commented on LOG4J2-355: Unfortunately, I found a bug so please, don't apply until I recreate a new patch. > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff, > LOG4J2-355_v2.patch, LOG4J2-355_v3.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Updated] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-355: --- Attachment: LOG4J2-355_v3.patch I updated the patch (LOG4J2-355_v3.patch) to the current trunk version. > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff, > LOG4J2-355_v2.patch, LOG4J2-355_v3.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756487#comment-13756487 ] Tibor Benke commented on LOG4J2-355: What do you think about this? Please, feel free to share your comments and thoughts about it. > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff, LOG4J2-355_v2.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756483#comment-13756483 ] Tibor Benke commented on LOG4J2-338: Any thoughts on it? It would be great if the log4j2 contained this feature in the GA release. > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Attachments: add_TLSSyslogAppender.zip > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Updated] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Benke updated LOG4J2-374:
---
Attachment: LOG4J2-374_v2.patch
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Affects Versions: 2.0-beta9
>Reporter: Tibor Benke
> Attachments: LOG4J2-374.patch, LOG4J2-374_v2.patch
>
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Commented] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755954#comment-13755954
]
Tibor Benke commented on LOG4J2-374:
You are right. I'm not good in giving names :)
Btw I'm going to attach a new patch. I edited the code, so now this feature is
part of the ThrowablePatternConverter class.
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Affects Versions: 2.0-beta9
>Reporter: Tibor Benke
> Attachments: LOG4J2-374.patch, LOG4J2-374_v2.patch
>
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Updated] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-355: --- Attachment: LOG4J2-355_v2.patch I added a "discardIfAllFieldsAreEmpty" boolean attribute to LoggerFields, so if all fields are empty during the evaluation in the RFC5424Layout, one can control that this SD-ELEMENT should be discarded or not. > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff, LOG4J2-355_v2.patch > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Updated] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Benke updated LOG4J2-374:
---
Attachment: LOG4J2-374.patch
Review ready patch :)
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Affects Versions: 2.0-beta9
>Reporter: Tibor Benke
> Attachments: LOG4J2-374.patch
>
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Commented] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752185#comment-13752185
]
Tibor Benke commented on LOG4J2-374:
I thought about it and I think we should use another pattern name than
%throwable in this case, because this improvement would imply the use of
%throwable{short} form, so it would be specious. Maybe the
DetailedShortThrowablePatternConverter or CustomShortThrowablePatternConverter
would be more expressive, so we could use the %dsThrowable or %csThrowable
names.
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Affects Versions: 2.0-beta9
>Reporter: Tibor Benke
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Updated] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
[
https://issues.apache.org/jira/browse/LOG4J2-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Benke updated LOG4J2-374:
---
Description:
That would be useful if we got more details about the method which threw the
exception. There is a "short" form, which contains these information, but there
can be some cases, when we need them separately.
For example we would write something like this:
{noformat}
%throwable{className}.%throwable{methodName}:%throwable{lineNumber}
%throwable{message}
{noformat}
And we would get this:
{noformat}
foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
{noformat}
I think we should only modify the ThrowablePatternConverter and
ThrowableFormatOptions classes and the documentation. What do you think about
it?
was:
That would be useful if we got more details about the method which threw the
exception. There is a "short" form, which contains these information, but there
can be some cases, when we need them separately.
For example we would write something like this:
%throwable{className}.%throwable{methodName}:%throwable{lineNumber}
%throwable{message}
And we would get this:
foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
I think we should only modify the ThrowablePatternConverter and
ThrowableFormatOptions classes and the documentation. What do you think about
it?
> Add more options to PatternLayout to display more detailed information about
> a Throwable
>
>
> Key: LOG4J2-374
> URL: https://issues.apache.org/jira/browse/LOG4J2-374
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
>Affects Versions: 2.0-beta9
>Reporter: Tibor Benke
>
> That would be useful if we got more details about the method which threw the
> exception. There is a "short" form, which contains these information, but
> there can be some cases, when we need them separately.
> For example we would write something like this:
> {noformat}
> %throwable{className}.%throwable{methodName}:%throwable{lineNumber}
> %throwable{message}
> {noformat}
> And we would get this:
> {noformat}
> foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
> {noformat}
> I think we should only modify the ThrowablePatternConverter and
> ThrowableFormatOptions classes and the documentation. What do you think about
> it?
--
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
[jira] [Created] (LOG4J2-374) Add more options to PatternLayout to display more detailed information about a Throwable
Tibor Benke created LOG4J2-374:
--
Summary: Add more options to PatternLayout to display more
detailed information about a Throwable
Key: LOG4J2-374
URL: https://issues.apache.org/jira/browse/LOG4J2-374
Project: Log4j 2
Issue Type: Improvement
Components: Layouts
Affects Versions: 2.0-beta9
Reporter: Tibor Benke
That would be useful if we got more details about the method which threw the
exception. There is a "short" form, which contains these information, but there
can be some cases, when we need them separately.
For example we would write something like this:
%throwable{className}.%throwable{methodName}:%throwable{lineNumber}
%throwable{message}
And we would get this:
foo.bar.ClassName.main:14 java.lang.ArithmeticException: / by zero
I think we should only modify the ThrowablePatternConverter and
ThrowableFormatOptions classes and the documentation. What do you think about
it?
--
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
[jira] [Commented] (LOG4J2-168) Include arbitrary message fields in RFC-5424 structured data
[ https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742328#comment-13742328 ] Tibor Benke commented on LOG4J2-168: I created a new issue: https://issues.apache.org/jira/browse/LOG4J2-355 And I also uploaded the patch. > Include arbitrary message fields in RFC-5424 structured data > > > Key: LOG4J2-168 > URL: https://issues.apache.org/jira/browse/LOG4J2-168 > Project: Log4j 2 > Issue Type: Bug > Components: Layouts >Affects Versions: 2.0-beta5 > Environment: N/A >Reporter: Scott Severtson >Priority: Minor > Fix For: 2.0-beta8 > > Attachments: include-arbitrary-fields-in-mdc-2.patch, > include-arbitrary-fields-in-mdc.patch > > > We'd really like to see the logger and/or location be included in RFC-5424 > structured data. As such, we've developed a small patch to allow arbitrary > PatternLayout names to be configured on the SyslogAppender, which are then > included in the structured data. > Patch to follow shortly. -- 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
[jira] [Updated] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
[ https://issues.apache.org/jira/browse/LOG4J2-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-355: --- Attachment: add_multime_SD_ELEMENT_support.diff > Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message > - > > Key: LOG4J2-355 > URL: https://issues.apache.org/jira/browse/LOG4J2-355 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.0-beta9 >Reporter: Tibor Benke > Attachments: add_multime_SD_ELEMENT_support.diff > > > The patch contains the modifications to support the feature and I also > refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Created] (LOG4J2-355) Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message
Tibor Benke created LOG4J2-355: -- Summary: Add support for multiple SD-ELEMENTs in a RFC 5424 syslog message Key: LOG4J2-355 URL: https://issues.apache.org/jira/browse/LOG4J2-355 Project: Log4j 2 Issue Type: Improvement Components: Core Affects Versions: 2.0-beta9 Reporter: Tibor Benke The patch contains the modifications to support the feature and I also refactored some code in the RFC5424Layout.java file. -- 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
[jira] [Commented] (LOG4J2-168) Include arbitrary message fields in RFC-5424 structured data
[
https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740983#comment-13740983
]
Tibor Benke commented on LOG4J2-168:
I think we should only modify the LoggerFields, RFC5424Layout and
SyslogAppender classes (and the TLSRFC5424Layout and TLSSyslogAppender classes
after their merge). I'm not sure about one thing: Can we use arrays with
@PluginElement? Like this:
@PluginElement("LoggerFields") final LoggerFields[] loggerFields
And I also suggest that if no name specified in the LoggerFields, we should add
its key-value pairs to the default mdc SD-ELEMENT. If nobody has quarrel with
it, I'll implement it.
> Include arbitrary message fields in RFC-5424 structured data
>
>
> Key: LOG4J2-168
> URL: https://issues.apache.org/jira/browse/LOG4J2-168
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
>Affects Versions: 2.0-beta5
> Environment: N/A
>Reporter: Scott Severtson
>Priority: Minor
> Fix For: 2.0-beta8
>
> Attachments: include-arbitrary-fields-in-mdc-2.patch,
> include-arbitrary-fields-in-mdc.patch
>
>
> We'd really like to see the logger and/or location be included in RFC-5424
> structured data. As such, we've developed a small patch to allow arbitrary
> PatternLayout names to be configured on the SyslogAppender, which are then
> included in the structured data.
> Patch to follow shortly.
--
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
[jira] [Commented] (LOG4J2-168) Include arbitrary message fields in RFC-5424 structured data
[ https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740953#comment-13740953 ] Tibor Benke commented on LOG4J2-168: Does the log4j2 support multiple SD-ELEMENTs in an RFC 5424 message? For example: <135>1 2013-08-15T11:47:44+02:00 10.30.255.247 APP-NAME PID MSGID [stuff@32473 foo="Foo" bar="Bar"][otherStuff@32473 baz="Baz" qux="Qux"] Some message I think it'd be nice to write something like this: Then we could structure more the log messages. What are your opinions? > Include arbitrary message fields in RFC-5424 structured data > > > Key: LOG4J2-168 > URL: https://issues.apache.org/jira/browse/LOG4J2-168 > Project: Log4j 2 > Issue Type: Bug > Components: Layouts >Affects Versions: 2.0-beta5 > Environment: N/A >Reporter: Scott Severtson >Priority: Minor > Fix For: 2.0-beta8 > > Attachments: include-arbitrary-fields-in-mdc-2.patch, > include-arbitrary-fields-in-mdc.patch > > > We'd really like to see the logger and/or location be included in RFC-5424 > structured data. As such, we've developed a small patch to allow arbitrary > PatternLayout names to be configured on the SyslogAppender, which are then > included in the structured data. > Patch to follow shortly. -- 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
[jira] [Comment Edited] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733307#comment-13733307 ] Tibor Benke edited comment on LOG4J2-338 at 8/8/13 9:31 AM: It contains the patch, the certificates to test and a sample log4j2.xml configuration. The JavaDoc and the site documentation has not been written yet, but if you say that the TLSSyslogAppender can be the part of the Log4j2, I will write them. was (Author: btibi): It contains the patch, the certificates to test and a sample log4j2.xml configuration. > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Attachments: add_TLSSyslogAppender.zip > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Updated] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Benke updated LOG4J2-338: --- Attachment: add_TLSSyslogAppender.zip It contains the patch, the certificates to test and a sample log4j2.xml configuration. > Add TLS support to SyslogAppender > - > > Key: LOG4J2-338 > URL: https://issues.apache.org/jira/browse/LOG4J2-338 > Project: Log4j 2 > Issue Type: New Feature > Components: Appenders, Core >Reporter: Tibor Benke > Attachments: add_TLSSyslogAppender.zip > > > Currently, there is no TLS support in SyslogAppender. > It would be very nice if one could send encrypted syslog messages to syslog > daemons. > I think the use cases are obvious: you want to protect your syslog messages > against masquerade, modification and disclosure. -- 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
[jira] [Created] (LOG4J2-338) Add TLS support to SyslogAppender
Tibor Benke created LOG4J2-338: -- Summary: Add TLS support to SyslogAppender Key: LOG4J2-338 URL: https://issues.apache.org/jira/browse/LOG4J2-338 Project: Log4j 2 Issue Type: New Feature Components: Appenders, Core Reporter: Tibor Benke Currently, there is no TLS support in SyslogAppender. It would be very nice if one could send encrypted syslog messages to syslog daemons. I think the use cases are obvious: you want to protect your syslog messages against masquerade, modification and disclosure. -- 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
