Thanks for the very nice document. Logging has been a source of complexity since the beginning of Beam, and upgrading to SLF4J2 is getting urgent.
I do have big picture questions/concerns: - For non-portable runners/pipelines, shouldn't the runner totally control logging backends so that it can capture logs correctly? - For portable runners, shouldn't the SDK harness totally control logging backends so it can ship logs out of the container correctly? Can you explain the intended use of having the user override the backend? (I totally understand that since we don't control dependencies we need all the frontend bridges) Kenn On Tue, Feb 4, 2025 at 3:15 PM Shunping Huang <mark.sphu...@gmail.com> wrote: > Hi everyone, > > I put together a short doc to summarize the existing logging > infrastructure(dependencies) in Beam Java and outline a plan to improve it. > Basically, we are on the path towards slf4j 2.x. > > > https://docs.google.com/document/d/1IkbiM4m8D-aB3NYI1aErFZHt6M7BQ-8eCULh284Davs/edit?usp=sharing > > If you are interested in this topic, please take a look and share any > feedback. > > Regards, > > Shunping >
