Zap Concepts: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 8: | Line 8: | ||
=Overview= | =Overview= | ||
Zap is .... | |||
Logging is performing by first creating a <code>Logger</code> object. Each logging invocation creates a log event with key/value pairs. <font color=darkkhaki>What about the log message?</code>. Depending on the <code>encoder?</code>, the rendering of the log events can be controlled. Rendering. | |||
There is no global logger that can be used right away, though one can be configured. | |||
There are two APIs, <code>Logger</code> and <code>SugaredLogger</code>. | There are two APIs, <code>Logger</code> and <code>SugaredLogger</code>. | ||
The supported logging levels are: .... Errors require special attention. | |||
Revision as of 19:49, 13 March 2024
Internal
TODO
Deplete from Zap_Concepts_TODEPLETE
Overview
Zap is ....
Logging is performing by first creating a Logger object. Each logging invocation creates a log event with key/value pairs. What about the log message?. Depending on the encoder?, the rendering of the log events can be controlled. Rendering.
There is no global logger that can be used right away, though one can be configured.
There are two APIs, Logger and SugaredLogger.
The supported logging levels are: .... Errors require special attention.