<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Zap - 标签 - 五岁博客</title>
        <link>https://fiveyoboy.com/tags/zap/</link>
        <description>Zap - 标签 - 五岁博客</description>
        <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>fiveyoboy@qq.com (五岁博客)</managingEditor>
            <webMaster>fiveyoboy@qq.com (五岁博客)</webMaster><lastBuildDate>Thu, 30 Apr 2026 00:00:00 &#43;0000</lastBuildDate><atom:link href="https://fiveyoboy.com/tags/zap/" rel="self" type="application/rss+xml" /><item>
    <title>Gin &#43; zap 实现日志链路追踪：RequestID 与 TraceID 完整方案</title>
    <link>https://fiveyoboy.com/articles/gin-zap-request-id-trace-id-log-tracing/</link>
    <pubDate>Thu, 30 Apr 2026 00:00:00 &#43;0000</pubDate>
    <author>五岁博客</author>
    <guid>https://fiveyoboy.com/articles/gin-zap-request-id-trace-id-log-tracing/</guid>
    <description><![CDATA[<p>在实际的 Go 后端项目中，当并发请求量上来之后，你会发现一件很头疼的事情——日志全混在一起了。某个接口报错了，你想从日志里找到完整的调用链路，却发现不同请求的日志交织在一起，根本分不清哪条日志属于哪个请求。</p>]]></description>
</item>
</channel>
</rss>
