I haven't done Java much lately, but one thing that would be nice would be some good documentation/examples on how and when to use the different artifacts/dependencies for Log4j. I have never used a BOM with Maven before, so I'm not sure how I would use it or why I would. I suspect that people who are coming into this for the first time have similar problems getting started, since there are a large number of ways to set it up.
-Robert Middleton On Fri, Jul 7, 2023 at 4:05 PM Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Funny you should ask. > > At the moment I am working on a more generalized version of > MutableThreadContextMapFilter. I envision a Filter that will be able to > reconfigure itself dynamically by querying a service. We have implemented > such as service at my employer but I would like to include it with the > component. Thus I plan on creating a separate logging-log4j-debug repo for > this. My hope is that this will also be able to dynamically update Logger > levels, so this should provide a universal way to update sets of servers. So > I am not sure if the repo name is accurate for what I actually want to > accomplish. > > Piotr seems to have being able to move log4j-async to its own module in his > focus. That is something I would definitely like to see as hopefully it can > simplify core. I would target this at 3.x only though. > > I also think adding better monitoring support would be useful. Any > integration that we can do with open-tracing/open-telemetry would be very > important as well as making sure we integrate well with Datadog/New > Relic/Dynatrace, etc. > > We really need to do something with the Jira backlog. I would bet at least > 50% should be closed but it takes time to look at each one to determine if it > is still valid or not. Anything that is valid should actually get worked on > or closed as won’t do if we never plan to work on it. > > Separating the API into its own web site should be a high priority IMO. In > fact, I am wondering if we really needed a 3.0 for the API. > > I definitely want to improve Log4j-Audit to make it more usable. It is a bit > complicated and the UI needs to be completely redone. > > Personally, I want to spend more time on my blog. I haven’t written anything > in a few years. I really want to push the work Piotr did on the transformer. > I have started integrating that into a few of my services at work and so far > it is completely transparent. I haven’t done any real world benchmarks with > it though and I’d like to do that. > > This list is just my immediate reaction to your question. I am quite sure > there are just as many things I have forgotten about as what is listed above. > > Ralph > > > > > On Jul 7, 2023, at 11:07 AM, Matt Sicker <m...@musigma.org> wrote: > > > > Now that we have Log4j 3’s first alpha release out along with some nifty > > release tooling, I’d like to discuss the near future of the project. I’ll > > have time to work on some of this at my day job, but that requires some > > future planning first. Besides the DI system changes that I’m still working > > on, what else did we want to finish up in the alpha releases? I know > > there’s still more module splitting that could possibly be done. > > > > What are some things that you’d like to do? And things you’d like to see > > get done but can’t necessarily do yourself? Or things you’d like to > > collaborate on? >
