gRPC-go disable - minimise logging?

<p>I&#39;ve been having a real struggle with gRPC-go and being so verbose and know they plan to add different verbosity levels - however has anyone else experienced this and come up with a reasonable solution?</p> <p>I am mostly referring to how when you call something to the nature of:</p> <pre><code>client.Close() </code></pre> <p>causes the server to log:</p> <pre><code>transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:50001-&gt;127.0.0.1:50829: read: connection reset by peer </code></pre> <p>on what appears to be exponential back-off.</p> <hr/>**评论：**<br/><br/>schumacherfm: <pre><p>Build your own log wrapper and add it like:</p> <pre><code>grpclog.SetLogger(grpcLogTestWrap{}) </code></pre> <p>I&#39;m using that pattern while testing gRPC backends for an ESI tag middleware.</p> <p>I also hate their global logger. Terrible pattern for a library.</p></pre>nastus: <pre><p>Thanks! </p></pre>pbo_: <pre><p>You can set your own gRPC logger using:</p> <p>google.golang.org/grpc/grpclog.SetLogger()</p> <p>But be aware that it must be called from init() functions only.</p> <p>You can check out etcd sources to see how CoreOS guys have overcome this limitation: <a href="https://github.com/coreos/etcd/blob/master/clientv3/logger.go" rel="nofollow">https://github.com/coreos/etcd/blob/master/clientv3/logger.go</a></p></pre>nastus: <pre><p>That&#39;s a good real world example, thanks :)</p></pre>