
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sun, 28 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/stack-trace/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces.en</guid>
    <title>Reading Logs and Stack Traces Like a Detective</title>
    <link>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces.en</link>
    <description>A stack trace is a crime scene; logs are witness statements. How to read a stack trace top to bottom (the top is where it blew up, the bottom is the origin), follow the &quot;caused by&quot; chain, use structured/JSON logging, correlate requests with trace_id, dig through logs with grep/jq/ripgrep, and use log levels and sampling. The detective skill of treating logs and traces as evidence.</description>
    <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>logging</category><category>debugging</category><category>stack-trace</category><category>observability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces.ja</guid>
    <title>ログとスタックトレースを探偵のように読む</title>
    <link>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces.ja</link>
    <description>スタックトレースは事件現場、ログは目撃者の証言です。スタックトレースを上から下へ読む方法（一方の端は壊れた場所、もう一方の端は発端）、「caused by」の連鎖の追跡、構造化・JSONロギング、相関IDとtrace_id、grep・jq・ripgrepでログを掘る、ログレベルとサンプリングまで。ログとトレースを証拠として扱う探偵の技術。</description>
    <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>logging</category><category>debugging</category><category>stack-trace</category><category>observability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces</guid>
    <title>로그와 스택트레이스를 탐정처럼 읽기</title>
    <link>https://www.youngju.dev/blog/2026-06-28-reading-logs-and-stack-traces</link>
    <description>스택트레이스는 사건 현장이고, 로그는 목격자 진술입니다. 스택트레이스를 위에서 아래로 읽는 법(맨 위는 터진 곳, 맨 아래는 발단), &quot;caused by&quot; 사슬 추적, 구조화·JSON 로깅, 상관관계 ID와 trace_id, grep·jq·ripgrep으로 로그 파헤치기, 로그 레벨과 샘플링까지. 로그와 트레이스를 증거처럼 다루는 탐정의 기술.</description>
    <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>logging</category><category>debugging</category><category>stack-trace</category><category>observability</category>
  </item>

    </channel>
  </rss>
