Hey Zili! It is good to see you at Logging Services!
[See my comments inline.] On Sat, Nov 22, 2025 at 5:32 PM tison <[email protected]> wrote: > It borrows many concepts from log4j and logback, and it is used in > production handling millions/s of logs, so IMO it's relatively solid. > Would you mind providing a little bit more context about its usage, please? [I know it is very hard to probe this for F/OSS, but I'd appreciate any information you can provide on this.] Which companies use it? What are the deployment contexts? Logger of a service? (Consider an Elasticsearch cluster logging using Log4j.) Logger of client/server application? (Consider a custom Spring Boot application.) Which appenders/layouts are used most? "millions/s" of logs? Can you quantify this more in detail, please? > I'm considering moving it to the ASF, but I'd first ask for some > logging devs review on the APIs if anyone here has some spare time. > I think Logging Services is certainly the right place to collect feedback on logging system APIs. The community, including maintainers, possesses a wealth of experience on the subject. IMHO, we can indeed support you there. > I'm considering moving it to the ASF Would you mind sharing your motivation and expectation for this move, please? Personally, I'd be very happy to see Logging Services supporting the Rust ecosystem. That being said, AFAICT, 1) we're pretty much understaffed (Log4j PRs are almost always reviewed by only two people, and Log4net/Log4cxx need Java maintainers' +1s to cut releases due to insufficient number of PMC members with .NET/C++ expertise), and 2) none of the maintainers have serious work experience with Rust. Given the current status quo, I am concerned about slowing down the Logforth development (due to ASF release policies taking days to cut a release) and not being able to contribute to the project meaningfully (due to lack of Rust expertise). I am curious to hear your thoughts. Cheers!
