<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jaeger on 黄文卓 | DevOps Engineer</title>
    <link>https://socake.github.io/tags/jaeger/</link>
    <description>Recent content in Jaeger on 黄文卓 | DevOps Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor>
    <webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster>
    <copyright>© 2026 Wenzhuo Huang</copyright>
    <lastBuildDate>Mon, 14 Jul 2025 09:52:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/jaeger/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>可观测性三支柱实战：Metrics/Logs/Traces 联动</title>
      <link>https://socake.github.io/posts/observability-three-pillars/</link>
      <pubDate>Mon, 14 Jul 2025 09:52:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/observability-three-pillars/</guid>
      <description>监控告诉你系统挂了，可观测性告诉你为什么挂。本文从三支柱的核心差异出发，讲透 Prometheus+Loki+Tempo 的联动排障流程，覆盖 OpenTelemetry 采集标准、Exemplar 原理与配置，以及可观测性建设的优先级策略。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/observability-three-pillars/featured.jpg" />
    </item>
    
    <item>
      <title>分布式链路追踪实战：Jaeger 与 Tempo 选型对比</title>
      <link>https://socake.github.io/posts/distributed-tracing-jaeger-tempo/</link>
      <pubDate>Thu, 10 Jul 2025 10:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/distributed-tracing-jaeger-tempo/</guid>
      <description>系统梳理 Jaeger 与 Tempo 的架构差异与适用场景，结合 OpenTelemetry SDK 插桩、TraceQL 查询、采样策略和 Traces/Metrics/Logs 关联，给出可落地的生产实战方案。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/distributed-tracing-jaeger-tempo/featured.jpg" />
    </item>
    
  </channel>
</rss>
