go-logger VS logr

For that reason I would advise to use any logging aggregators that have rich adapters and capabilities to add new ones, eg. something like this: https://github.com/InVisionApp/go-logger . Note that this particular project is now abandoned (serious mem leak I posted as PR was never merged; I use my custom, public fork for that reason) so it is worth to ask: does anyone know about anything more recent, active and maintained that implements similar concept?

logr

How about using https://github.com/go-logr/logr You’ll be able to swap concrete implementation easily which will allow you to try out different libs on the market without refactoring all your logic

I recommend https://github.com/go-logr/logr and you can choose implementation freely but zerolog/zap are optimized for speed.

For logging, I use https://github.com/go-logr/logr with https://github.com/uber-go/zap

I'd say it depends. If I write a package for others to use I usually don't include a logger at all and let the user decide what he wants to use. For any other project that needs logging I usually skip the interface to not have the struggle with finding one interface that fits all at least logrus and zap. We kinda agreed at the team to just use zap by now. One.thing i wanted to try tho is using sth like logr which provides an interface for the most commonly used loggers.

After writing a lot of libraries I really appreciate logr. There are plenty of times when my library needs to output debugging info, but it's not practical to do things like parse flags for verbosity level. With thus I can just log at a higher V level and be done with it.