Re: [GitHub] logging-log4j2 pull request #202: [LOG4J2-2391] Improve ThrowableProxy perfo...

My guess is that StackWalker provides additional information beyond the array of classes supplied by the SecurityManager, though I've not done a thorough analysis yet. A quick targeted benchmark of our current implementations: Benchmark Mode Cnt Sco

Re: [GitHub] logging-log4j2 pull request #202: [LOG4J2-2391] Improve ThrowableProxy perfo...

I have to wonder why using the security manager is faster than using StackWalker. StackWalker was created just for this purpose. Is the way it is implemented the problem? Ralph > On Aug 7, 2018, at 1:34 PM, cakofony wrote: > > GitHub user cakofony opened a pull request: > >https://githu

Re: [Log4j2] Supported Redis Appender

IOW, think clean room. G On Tue, Aug 7, 2018 at 11:50 AM Gary Gregory wrote: > If you provide a PR for this new appender, please make sure there is no > copying from GPL code... > Thank you! > Gary > > On Tue, Aug 7, 2018 at 10:57 AM Kevin Meurer > wrote: > >> That sounds good to me. I would b

Re: [Log4j2] Supported Redis Appender

If you provide a PR for this new appender, please make sure there is no copying from GPL code... Thank you! Gary On Tue, Aug 7, 2018 at 10:57 AM Kevin Meurer wrote: > That sounds good to me. I would be happy to update the site with > appropriate language on the different approaches when submitti

Re: [Log4j2] Supported Redis Appender

That sounds good to me. I would be happy to update the site with appropriate language on the different approaches when submitting the feature. I'll go ahead and write an appender implementation for you and other maintainers to review. I went ahead and opened LOG4J2-2400 to track implementation here

Re: Logging and containers

I had requested the HTTP appender a while back for potential use in writing directly to Elasticsearch which helps reduce the moving parts involved in any sort of log searching stack. There's also the option of hosting a Graylog server and writing directly to it through a socket appender, though I h

Re: [Log4j2] Supported Redis Appender

OK. I would recommend that the doc for the component describe that use case. I would think we also could add another page or two to the web site to compare the various ways of doing these things. Ralph > On Aug 7, 2018, at 8:44 AM, Kevin Meurer wrote: > > I completely agree that the typica

[log4j] Proposal for asynchronous formatting on reusable messages

Hi folks, I've filed LOG4J2-2399 with a proposal for supporting asynchronous message formatting on reusable messages, with a bit of background explaining why it would be ideal for my use case. I'd appreciate feedback on the idea. If we're happy with it, I have a bit of time this week to put togeth

Re: [Log4j2] Supported Redis Appender

I completely agree that the typical use case of Redis is a distributed cache. That said, it also functions well as a temporary queue for event data en route to another data store. For example, Redis may be used to improve the fault-tolerance of a logging pipeline by serving as an intermediary en ro

Re: [Log4j2] Supported Redis Appender

While I wouldn’t be opposed to a Redis Appender, I would find it a strange use of Redis. Normally, Redis is used as a distributed cache, not as a place to store log evens. Can you explain what the use case would be when using it? Ralph > On Aug 7, 2018, at 8:05 AM, Kevin Meurer wrote: > > Hi

[Log4j2] Supported Redis Appender

Hi all, I wanted to float the idea of folding a Redis log4j2 appender into the log4j2 repository or releasing a canonical version under the Apache license. As you might be aware, one repository currently exists to meet this need, but it is licensed un

JDK 11 , JDK 12 and JDK 8u192 Early Access builds are available on jdk.java.net

Hi Ralph, *JDK 11 Early Access  build 25 is available at : - **jdk.java.net/11/* * *JDK 11 entered Rampdown Phase 2 on 26-July [1]* o The overall feature set is frozen. No further JEPs will be targeted to this release. o We now turn our focus to P1 and P2 bugs. * Release notes