go-kit/kit

How to leverage kit/log logging in several .go files/libraries without producing an overwhelming amount of output?

Open

#565 opened on Jul 6, 2017

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (27,422 stars) (2,446 forks)batch import
enhancementhelp wanted

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?

Contributor guide

Tech stack
go
Domain
observabilitybackend
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programminglogging concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue asks about hierarchical logging in go kit to control debug output per file/library. It references log4cxx/log4net patterns. The maintainers could provide documentation or a logging middleware example that supports level based filtering per logger instance. Existing comments may contain suggestions; review them for potential solutions. No pull requests are linked.