ewintr
/
go-kit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

toc in logging doc

This commit is contained in:
Erik Winter 2022-04-07 06:12:17 +02:00
parent f79c535373
commit 77f78e3e6b
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/logging-in-golang.adoc
View File

@ -6,6 +6,13 @@ The subject of logging comes up every now and then, in every group of developers
Anyway, as with most things computing, I like logging to be simple and pragmatic. Over the years, these are the things I’ve come to consider important with this subject. Anyway, as with most things computing, I like logging to be simple and pragmatic. Over the years, these are the things I’ve come to consider important with this subject.
* #levels[Levels]
* #structured-logging-and-standard-messages[Structured logging and standard messages]
* #wrapping-loggers[Wrapping loggers]
* #advanced-structuring[Advanced structuring]
* #injecting-loggers-versus-returning-errors[Injecting loggers versus returning errors]
* #example-implementation[Example implementation]
== Levels == Levels
When thinking about what logging levels are appropriate, it helps to define the intended audience for a certain level and what information that audience should get out of it. In addition to that, it also helps to remember what goals and what information are already covered by other systems. When thinking about what logging levels are appropriate, it helps to define the intended audience for a certain level and what information that audience should get out of it. In addition to that, it also helps to remember what goals and what information are already covered by other systems.