github.com/voedger/voedger@v0.0.0-20240520144910-273e84102129/pkg/goutils/logger/README.md (about) 1 [](https://codecov.io/gh/heeus/core-logger) 2 # logger 3 4 Simple go logger with logging level. Default output will be like this: 5 6 ``` 7 09/29 13:29:04.355: *****: [core-logger.Test_BasicUsage:22]: Hello world arg1 arg2 8 09/29 13:29:04.373: !!!: [core-logger.Test_BasicUsage:23]: My warning 9 09/29 13:29:04.374: ===: [core-logger.Test_BasicUsage:24]: My info 10 09/29 13:29:04.374: ---: [core-logger.Test_BasicUsage:35]: Now you should see my Trace 11 09/29 13:29:04.374: !!!: [core-logger.Test_BasicUsage:41]: You should see my warning 12 09/29 13:29:04.374: !!!: [core-logger.Test_BasicUsage:42]: You should see my info 13 09/29 13:29:04.374: *****: [core-logger.(*mystruct).iWantToLog:55]: OOPS 14 ``` 15 16 See [impl_test.Test_BasicUsage](impl_test.go#L24) for examples 17 18 # Links 19 20 - [Why does the TRACE level exist, and when should I use it rather than DEBUG?](https://softwareengineering.stackexchange.com/questions/279690/why-does-the-trace-level-exist-and-when-should-i-use-it-rather-than-debug) 21 - [Good answer](https://softwareengineering.stackexchange.com/questions/279690/why-does-the-trace-level-exist-and-when-should-i-use-it-rather-than-debug/360810#360810)