Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make client logging configurable
See original GitHub issueIs your feature request related to a problem? Please describe. The Python and Go client libraries log - a lot. It’s annoying especially if you’re trying to use a form of structured logging, or just debug something you know is unrelated to Pulsar.
Describe the solution you’d like At bare minimum, there should be a way to just turn it off.
A more complete solution would allow configuring the logger in a way idiomatic to each language. For example, integrating with Python logging. I’m not 100% sure how.
Another option would be to allow redirecting the logs to a file instead of polluting stderr.
Describe alternatives you’ve considered Not sure if there’s a good alternative.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The client logging in python still seems non-configurable even after providing the log4cxx config file. Is it possible to configure to stop logging to stdout ?
It seems maybe this got held up due to the potential difficulty of sending log data from C++ up to python. How about just providing options to silence logging, and/or set the log level in the meantime?