How to leverage kit/log logging in several .go files/libraries without producing an overwhelming amount of output?
#565 aberto em 6 de jul. de 2017
Métricas do repositório
- Stars
- (27.422 stars)
- Métricas de merge de PR
- (Nenhuma PRs mesclada em 30d)
Description
I have experience with log4cxx and log4net that support hierarchical logging. I'd like to include a range of logging in my libraries and .go files but I'm not sure what the best approach is to keep the console output down when doing so.
If I have an issue I'll raise the level to debug to see the details. Even though I know the issue is likely in a single or handful of .go files, or maybe in a library, raising the level means seeing the debug output from everywhere I'm using logging that is part of the execution path. I could comment those log entries out but that's a lot of extra time.
Is there a generally accepted way of including logging in all of your .go files and methods without overwhelming yourself with output that you don't need to enable unless debugging that particular file?