Re: Effective use of logging with Graylog and other log aggregators

Oh, and I should add that this also relates to my other thread about binary layouts. I'd find that using binary layouts would be most useful for network appenders, though it can also be useful for when log aggregation daemons are run on every server to collect the output of log files, too. On 28 A

Effective use of logging with Graylog and other log aggregators

Log4j has all the necessary plugins to support numerous scenarios, and I've found three ways to support Graylog, for example: 1. GelfLayout + SocketAppender: send log messages straight to a Graylog server. Simplest setup (no additional dependencies required), but not the most reliable in theory. 2

New binary layouts

I made a ticket recently to add an AvroLayout. There are numerous other alternative libraries for binary serialization which are generally faster and better supported than Java serialization, though they all require additional dependencies. I also have an idea on abstracting out many of the struct

Re: [log4net] git repository is online

On 2017-04-28, Matt Sicker wrote: > Speaking of which, we use the Jenkinsfile style pipelines at my work, and > those are a bit less annoying to use than the web interface. Any idea if we > can use those here? builds.apache.org has a "Open Blue Ocean" button at the top, at least once you authenti

Re: [log4net] git repository is online

On 2017-04-28, Dominik Psenner wrote: > Stefan has mastered all levels that exist for making jenkins > configurations. :-) TBH, I haven't tried that so far and am not sure the necessary Jenkins plugins have been installed. This would be pretty low on my personal priority list, so if you get there

Re: [log4net] git repository is online

Speaking of which, we use the Jenkinsfile style pipelines at my work, and those are a bit less annoying to use than the web interface. Any idea if we can use those here? On 28 April 2017 at 10:07, Dominik Psenner wrote: > Stefan has mastered all levels that exist for making jenkins > configurati

Re: [log4net] git repository is online

Stefan has mastered all levels that exist for making jenkins configurations. :-) On 2017-04-28 17:05, Matt Sicker wrote: Can we? Most likely. Does anyone know how to configure it like that? 🤔 On 28 April 2017 at 10:01, Dominik Psenner wrote: When we see that jenkins works. Can we configure

Re: [log4net] git repository is online

Can we? Most likely. Does anyone know how to configure it like that? 🤔 On 28 April 2017 at 10:01, Dominik Psenner wrote: > When we see that jenkins works. Can we configure jenkins to attempt a > merge of pull requests and run the tests against that? ;-) > > > > On 2017-04-28 16:39, Stefan Bodewi

Re: [log4net] git repository is online

When we see that jenkins works. Can we configure jenkins to attempt a merge of pull requests and run the tests against that? ;-) On 2017-04-28 16:39, Stefan Bodewig wrote: Hi I've also re-configured Jenkins to use git, we'll see how that works out. Stefan

[jira] [Closed] (LOG4J2-428) Implement a GELF layout

[ https://issues.apache.org/jira/browse/LOG4J2-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-428. - > Implement a GELF layout > --- > > Key: LOG4J2-428 >

[jira] [Commented] (LOG4J2-1752) Add ISO8601 format to timestamp in JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988940#comment-15988940 ] Mikael Ståldal commented on LOG4J2-1752: If you want to try implementing this, co

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988936#comment-15988936 ] Mikael Ståldal commented on LOG4J2-1694: I did not find any reasonable way to do

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988932#comment-15988932 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988929#comment-15988929 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988930#comment-15988930 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988928#comment-15988928 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988931#comment-15988931 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988927#comment-15988927 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

Re: [log4net] git repository is online

Hi I've also re-configured Jenkins to use git, we'll see how that works out. Stefan

[jira] [Assigned] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1694: -- Assignee: (was: Mikael Ståldal) > Allow to easily add fields with fixed values to

Re: YamlLayout.toSerializable

Yes, I will remove it. On Fri, Apr 28, 2017 at 4:19 PM, Matt Sicker wrote: > Then that toSerializable() override is most likely a copy/paste error from > JsonLayout. > > On 28 April 2017 at 09:15, Mikael Ståldal > wrote: > > > YamlLayout always prefix each event with a line with "---". JsonLayo

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988908#comment-15988908 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

Re: YamlLayout.toSerializable

Then that toSerializable() override is most likely a copy/paste error from JsonLayout. On 28 April 2017 at 09:15, Mikael Ståldal wrote: > YamlLayout always prefix each event with a line with "---". JsonLayout is a > bit different since you don't want a comma before the first event. > > On Fri, A

Re: YamlLayout.toSerializable

YamlLayout always prefix each event with a line with "---". JsonLayout is a bit different since you don't want a comma before the first event. On Fri, Apr 28, 2017 at 4:02 PM, Matt Sicker wrote: > The YamlLayout should probably separate events by "--" or whatever the page > separator token is in

Re: YamlLayout.toSerializable

The YamlLayout should probably separate events by "--" or whatever the page separator token is in yaml (not a widely used feature). On 28 April 2017 at 03:14, Mikael Ståldal wrote: > YamlLayout has this method: > > @Override > public void toSerializable(final LogEvent event, final Writer writer)

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988840#comment-15988840 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

JDK 9 EA Build 167 and JDK 8u152 build 03 are available on jdk.java.net

Hi Nick, *JDK 9 Early Access* build 167 is available at the new location : - jdk.java.net/9/ A summary of all the changes in this build are listed here . One change that maybe of interest is : *JEP 291: Deprecate the Concu

Re: [log4net] git repository is online

On 2017-04-28 11:04, Stefan Bodewig wrote: Not really. But we need to update the log4net website. I'll see to it later today. Great! I planned to do that this evening around 22:00 CET, but the kids are probably going to interfere with these plans. :-D We should probably hold back deleting

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988497#comment-15988497 ] ASF subversion and git services commented on LOG4J2-1854: - Commit

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988498#comment-15988498 ] ASF subversion and git services commented on LOG4J2-1694: - Commit

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988495#comment-15988495 ] ASF subversion and git services commented on LOG4J2-1854: - Commit

Re: [log4net] git repository is online

On 2017-04-28, Dominik Psenner wrote: > On 2017-04-28 06:43, Stefan Bodewig wrote: >> Before svn goes read-only we may want to remove the contents of trunk >> and add a single README saying that we moved to git with pointers to the >> Apache repo as well as the new github mirror. > I thought that

YamlLayout.toSerializable

YamlLayout has this method: @Override public void toSerializable(final LogEvent event, final Writer writer) throws IOException { if (complete && eventCount > 0) { writer.append(", "); } super.toSerializable(event, writer); } As far as I can see, it shouldn't be there since you