Re: Console performance

2018-04-02 Thread Chandra
file directly. Best, Chandra On 2 Apr 2018, 10:38 PM +0530, Matt Sicker , wrote: > I always set direct="true" on console appenders (it's false by default > because we added that option later). > > On 2 April 2018 at 12:05, Gary Gregory wrote: > > > I'

Re: Log4j Audit

2018-02-05 Thread Chandra
Best, Chandra On 5 Feb 2018, 8:44 PM +0530, Ralph Goers , wrote: > Remko, > > Thanks for all the good feedback! That is exactly what I was looking for. > > I won’t answer the questions you posed here. Instead, I will try to correct > the web site to see if it does the job.

RE: Extend daily log file appender

2018-02-02 Thread Chandra
I believe custom pattern converter should suffice in your case. You could create a converter which encrypts the log event data. Reg, Chandra On 2 Feb 2018, 5:53 PM +0530, Walter Heestermans (TME) , wrote: > We like to do the encryption outside the application logging,a nd centralized >

Re: Extend daily log file appender

2018-02-02 Thread Chandra
any issues to log encrypted data directly? Reg, Chandra On 2 Feb 2018, 4:31 PM +0530, Walter Heestermans (TME) , wrote: > Hi, > > For GDPR we should have some log4 log appender (extended from daily log file > appender) that encrypts the log information. > > Anybody aware of s

Re: Compression on rolling leads to OOM

2017-11-16 Thread Chandra
Windows > > does), but you can execute and control processes at least. > > > > On 16 November 2017 at 12:28, Ralph Goers > wrote: > > > > > Sure, why not? > > > > > > Ralph > > > > > > > On Nov 16, 2017, at 11:24 AM, C

Re: Compression on rolling leads to OOM

2017-11-16 Thread Chandra
es at least. > > On 16 November 2017 at 12:28, Ralph Goers wrote: > > > Sure, why not? > > > > Ralph > > > > > On Nov 16, 2017, at 11:24 AM, Chandra > aachen.de> wrote: > > > > > > with-in log4j? > > > > > > On 16 Nov

Re: Compression on rolling leads to OOM

2017-11-16 Thread Chandra
with-in log4j? On 16 Nov 2017, 11:46 PM +0530, Ralph Goers , wrote: > I could see forking a process instead of spawning a thread to perform the > compression as a viable approach. > > Ralph > > > On Nov 16, 2017, at 10:01 AM, Chandra > > wrote: > > > > th

Re: Compression on rolling leads to OOM

2017-11-16 Thread Chandra
on my app than an external process. which is why I was looking for an “agent” . thanks! chandra On 16 Nov 2017, 9:57 PM +0530, Matt Sicker , wrote: > I brought up Snappy only because I used their off-heap API recently. Snappy > is more about real time compression rather than size (I think

Re: Compression on rolling leads to OOM

2017-11-16 Thread Chandra
zip would work in-fact. Ideally a reliable agent something like `FileBeat` would be great for this situation. :-/ Best, Chandra On 16 Nov 2017, 9:08 PM +0530, Matt Sicker , wrote: > What if compression worked off-heap like with some of the native > implementations of codecs? I'm thinki

Compression on rolling leads to OOM

2017-11-15 Thread Chandra
_full-proof_ solution for this situation. Any thoughts, suggestions would be useful and appreciated. thanks! Chandra On 16 Nov 2017, 10:01 AM +0530, Ralph Goers , wrote: > Unless someone objects I plan to start the release process for Log4j 2.10 > tomorrow. I had wanted to include a fix for

Re: appender Failover has no parameter that matches element Failovers

2017-10-13 Thread Chandra
Can you post your log4j2 configuration? I’ve seen some issues while using failover appender. On 13 Oct 2017, 6:00 PM +0530, gaurav9...@gmail.com , wrote: > Hi log4j2 developers, > > I am getting following error while configuring 'failoverappender' for my > primary 'console appender': > > append

Re: picocli in log4j

2017-08-07 Thread Chandra
+1 for picocli, I looked into it some time ago and looked pretty good. In-fact, I wanted to use it for my own project for `JvmTop`. btw, where are we using `Jcommander` in log4j2? thanks, Chandra On 7 Aug 2017, 8:32 PM +0530, Matt Sicker , wrote: > I have no objections. I do like your libr

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

2017-07-18 Thread chandra (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091742#comment-16091742 ] chandra commented on LOG4J2-1883: - Although, it's nice to maintain a nanosec

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

2017-07-05 Thread Chandra
fix. Best, Chandra On 5 Jul 2017, 9:23 PM +0530, Dominik Psenner , wrote: > Hi, > > I'm currently in the process of writing the build pipeline for log4net. > During this process errors will continue to pop up and I understand that > people don't want to be nagged. Therefore

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

2017-07-05 Thread Chandra
hi, this is my 2nd reminder. this has become a regular,  I see my mailbox full of build failure emails. Isn’t there anyone responsible suppressing this? — I’d be force to unsubscribe, for the love of god, please handle this! thanks,Chandra On 5 Jul 2017, 8:56 PM +0530, Apache Jenkins Server

Re: Build failed in Jenkins: logging-log4net » feature/Build-mono-on-ubuntu #13

2017-07-03 Thread Chandra
Am I the only one bothered by this Jenkins failure message? In the past couple of days, I’ve received over 50+ messages of the same. Anyone responsible for this can take necessary action to stop this spamming the mailbox? thanks, Chandra On 3 Jul 2017, 2:01 PM +0530, Apache Jenkins Server

Re: PR#72 build failure.

2017-04-24 Thread Chandra
Perfect. thanks Matt! Hopefully, more PRs in the future :) thanks, Chandra On 24 Apr 2017, 12:59 PM +0530, Matt Sicker , wrote: > Thanks for the PR! I've gone and remerged it to make sure GitHub was > updated properly as well. > > On 20 April 2017 at 13:47, Chandra wrote:

Re: PR#72 build failure.

2017-04-20 Thread Chandra
Sounds good and I *really* like the auto tagging of PR/s with Jira. Not sure how ASF works, at least I haven’t been any real contributor to any Apache projects _yet_. log4j2 seemed to be a good start! thanks, Chandra On 21 Apr 2017, 12:14 AM +0530, Matt Sicker , wrote: > We have it set up a

Re: PR#72 build failure.

2017-04-20 Thread Chandra
JAR: Problem creating jar: Execution exception: Java heap space -> [Help 1] so, you guys aren’t using the travis for CI? oO thanks, Chandra On 20 Apr 2017, 11:59 PM +0530, Matt Sicker , wrote: > That was a Travis build failure, right? That system is even less reliable > than our norma

[jira] [Comment Edited] (LOG4J2-1883) Timestamp does not seem to support microseconds level

2017-04-19 Thread chandra (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976019#comment-15976019 ] chandra edited comment on LOG4J2-1883 at 4/20/17 3:53 AM: --

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

2017-04-19 Thread chandra (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976019#comment-15976019 ] chandra commented on LOG4J2-1883: - With all the discussion above, it is a good FY

Re: PR#72 build failure.

2017-04-19 Thread Chandra
Yeah. I believe you. was just wondering why the all build failures. ;) thanks, Chandra On 20 Apr 2017, 5:33 AM +0530, Matt Sicker , wrote: > Don't worry about the build failure. We can still merge it. :) > > On 19 April 2017 at 00:43, Chandra wrote: > > > Hi List, >

PR#72 build failure.

2017-04-19 Thread Chandra
Hi List, I had a minor update on the documentation for which I sent a pull request. Not sure what happened but, the travis build failed. I see a lot of build failures from the PRs, any reason for that? Here’s my pull request. https://github.com/apache/logging-log4j2/pull/72 thanks, Chandra

PR#72 build failure.

2017-04-18 Thread Chandra
Hi List, I had a minor update on the documentation for which I sent a pull request. Not sure what happened but, the travis build failed. I see a lot of build failures from the PRs, any reason for that? Here’s my pull request. https://github.com/apache/logging-log4j2/pull/72 thanks, Chandra