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.
Filtering chatty libraries
See original GitHub issueIn general, debug output is what I’m looking for, and I’d like to get it from all dependent libraries. Using the snippet for integrating with the logging library, all is mostly well.
However, if left unchecked, boto3 and requests are good examples of libraries which are too chatty and log a lot of records that are generally not useful. But it’s not obvious to me how to add loguru-side sinks in such a way that I can specify, x, y, and z packages ought to be filtered to INFO logs, and otherwise unspecified packages ought to continue logging at DEBUG.
Would the canonical method be adding a filter param to every add call and doing a separate level comparison at the point where i’m comparing against the logger?
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (9 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
Implemented! Thanks again for your patience and your feedback. It will be available in the
v0.4.0coming soon. 👍Yeah, don’t worry, I was just genuinely interested to know why you thought it was better to display all logs by default. I guess it entirely depends on the user. I think it might surprise some people to see logs which are not their own, this is why there is the possibility to
.disable()them.Anyway, I will implement the “dict-filtering” in the next few days and publish a new release shortly after that. 👍