go.uber.org/zap and Graylog

<p>Who has experience with wiring Ueber&#39;s zap logging package to Graylog? Would you share any insights? I found several open source packages to connect zap to a GELF host. Do you have any experience with one? Which one would you recommend? Any comments are welcome! </p> <hr/>**评论：**<br/><br/>014a: <pre><p>Generally you shouldn&#39;t be worrying about where logs go from the context of your application. Its one of the <a href="https://12factor.net/logs" rel="nofollow">12 Factor guidelines</a>. </p> <p>Dump your logs in JSON to stdout, then have a Graylog sink running in the environment. </p> <p>Of course this doesn&#39;t work for every deployment topology, so your mileage may vary. But if your deployment topology doesn&#39;t support it, treat that as a signal that maybe something there needs improvement at some point. </p></pre>drvd: <pre><blockquote> <p>Of course this doesn&#39;t work for every deployment topology</p> </blockquote> <p>Yes. That is the whole reason I need to connect zap to GELF. If I <em>could</em> I&#39;d just log to stdout but I cannot. And yes, it would be nice if the available infrastructure would be 12 Factor compliant, but it is not and it cannot be changed and that&#39;s why I asked about experience with connecting zap to Graylog. </p></pre>014a: <pre><p>In that case, look into creating a new <a href="https://godoc.org/go.uber.org/zap/zapcore#WriteSyncer" rel="nofollow">zapcore.WriteSyncer</a> that supports GrayLog. Depending on which Graylog library you&#39;re using, you might need to write your own abstraction type to abide by an io.Writer, but once you have that it should be pretty straightfoward; create the WriteSyncer, use it to create a new zapcore.Core with an appropriate message encoder (likely just JSON), then pass that to zap.New.</p></pre>drvd: <pre><p>Thanks. The idea was less to write our own than to use an existing one. Does anybody have experience with and <em>existing</em> integration?</p></pre>