rmannibucau opened a new pull request, #8320:
URL: https://github.com/apache/hop/pull/8320

   Overall idea is to move to a real logger implementation, there are multiple 
pitfalls with current manual buffering/filewriter:
   
   * it is not very customizable (structured logging is hard to do for example)
   * it requires to use /dev/null as workaround when in a docker container and 
enable stdout/stderr
   * it is not extensible with common appenders easily even with slf4j listener 
- kafka my friend to cite it ;)
   * it is not easy to auto-instrument (opentelemetry-javaagent or k8s 
integrations for ex, slf4j is built-in, not custom integrations)
   * there is no real notion of MDC or future work on observability
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [X] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [ ] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [-] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [X] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [X] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to