<p>Do you instantiate a new logger within the HandlerFunc? Do you use a global logger (Zap's FAQ discourages this)? Do you write a wrapper around the HandlerFunc that lets you pass in a logger instance from main?</p>
<hr/>**评论：**<br/><br/>iygwaz: <pre><p>Followup question: Is there any way to group logs from a single request with some sort of reference number? I was thinking of using a goroutine ID or something like that but apparently you can't access them (<a href="https://stackoverflow.com/questions/19115273/looking-for-a-call-or-thread-id-to-use-for-logging" rel="nofollow">https://stackoverflow.com/questions/19115273/looking-for-a-call-or-thread-id-to-use-for-logging</a>)</p></pre>Rafikithewd: <pre><p>You can generate a request id and add it to the request context </p>
<p>Example: <a href="https://joeshaw.org/revisiting-context-and-http-handler-for-go-17/" rel="nofollow">https://joeshaw.org/revisiting-context-and-http-handler-for-go-17/</a></p></pre>Rafikithewd: <pre><p>I personally use either logrus or apex/log for my projects </p>
<p>They have a singleton approach so you can configure the logger in main() but to use it later you just have to import the package </p>
<p><a href="https://medium.com/@47fd6a5307cc/e8d9627f4a9a" rel="nofollow">https://medium.com/@47fd6a5307cc/e8d9627f4a9a</a></p></pre>quiI: <pre><p>Logging is just like any other dependency, like a `FooService`</p>
<p>Use DI to pass in your dependencies, then they are easy to test and dont rely on global variables.</p>
<p>This might help <a href="https://quii.gitbook.io/learn-go-with-tests/standard-lib-essentials/http-server" rel="nofollow">https://quii.gitbook.io/learn-go-with-tests/standard-lib-essentials/http-server</a> </p></pre>
