Re: [chainsaw] Status change?

+1 Allow me to make some corrections: `XmlLayout` is dropped in Log4j 3, not in Log4j 2. Logstash (the L in the ELK, Elasticsearch-Logstash-Kibana, stack) supports reading logs from a file formatted using a particular pattern. You combine Filebeat with grok filter

Re: [chainsaw] Status change?

Thank you for spending time working on it Christian. I started contributing to Chainsaw in 2003. I agree. It's time. The primary benefit of Chainsaw was its built-in support for real-time tailing of ssh-accessible pattern-layout based logs - something Kibana doesn't support well, and something n

[chainsaw] Status change?

Hello we have had Chainsaw for a long time in our product list, and I can totally see that some - myself included - are emotionally attached to it. However, due to my work on it, I have given it some additional thought. After working with the Chainsaw code base for a while, I saw that many feat

Re: Clean site repo

Hi Ralph, On Tue, 6 Feb 2024 at 17:47, Ralph Goers wrote: > > When you say “hard to work with it” what does that mean? All that should ever > be required is to do I am mostly concerned by the great amount of files on the website. Most of them are hidden, since we don't provide links to `/log4j/

Re: Clean site repo

When you say “hard to work with it” what does that mean? All that should ever be required is to do git rebase asf-staging I have never had that take more than a few seconds. Are you really saying that the staging site is hard to work with? My understanding is that “we” are working on reworki

Clean site repo

Hi all, The current `asf-site` branch of the `logging-log4j-site` repo has about 450k files, which makes it very hard to work on it. Most of those are websites of old releases that I doubt anybody (except search engines) visits. Those websites also pollute search engine results: several times I f

Re: [log4j] Nested logging and async. message formatting

Thanks so much for thinking along with me Piotr in this pretty sophisticated puzzler. Regarding your following statements... On Mon, Feb 5, 2024 at 8:43 PM Piotr P. Karwasz wrote: > I would prefer for the two event factories **not** to call > `Message#getFormattedMessage` at all. > ... > Both iss

Re: Revamp of asynchronous logging

Hi Matt, On Mon, 5 Feb 2024 at 22:37, Matt Sicker wrote: > > For #3, I agree that we should perform formatting on the application thread > before transferring control to an asynchronous thread. I am not sure if we always need to format the message (the `log4j2.formatMsgAsync` property and and t

[ANNOUNCE] Apache Log4j Scala 13.1.0 released

Apache Log4j Scala team is pleased to announce the 13.1.0 release. This project provides a Scala-friendly interface to log against the Log4j API. For further information (support, download, etc.) see the project website[1]. [1] https://logging.apache.org/log4j/scala === Release Notes This minor

[RESULT][VOTE] Release Apache Log4j Scala 13.1.0

Adding my +1. With that, the release passes with 3 binding +1 votes from Piotr, Christian, and me. I will continue the release process. On Thu, Feb 1, 2024 at 11:31 AM Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j Scala 13.1.0. > > Website: https://logging.staged.apache.org