
  <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>Fri, 15 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/pixie/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive.en</guid>
    <title>eBPF Observability 2026 — Pixie / Parca / Cilium Hubble / Tetragon / Beyla / Coroot / Falco Deep Dive</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive.en</link>
    <description>A complete map of the eBPF ecosystem as of 2026. Compares Pixie, Parca, Cilium Hubble, Tetragon, BCC/bpftrace, OpenTelemetry eBPF Collector, Grafana Beyla, Coroot, Inspektor Gadget, Kepler and Falco — plus the CO-RE revolution and Windows/macOS ports.</description>
    <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ebpf</category><category>observability</category><category>pixie</category><category>parca</category><category>cilium</category><category>hubble</category><category>tetragon</category><category>beyla</category><category>coroot</category><category>falco</category><category>opentelemetry</category><category>kubernetes</category><category>2026</category><category>deep-dive</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive.ja</guid>
    <title>eBPF 観測性 2026 — Pixie / Parca / Cilium Hubble / Tetragon / Beyla / Coroot / Falco 徹底ガイド</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive.ja</link>
    <description>2026 年時点の eBPF エコシステムを一気にまとめる。Pixie、Parca、Cilium Hubble、Tetragon、BCC/bpftrace、OpenTelemetry eBPF Collector、Grafana Beyla、Coroot、Inspektor Gadget、Kepler、Falco を比較し、CO-RE 革命と Windows/macOS への移植まで扱う。</description>
    <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ebpf</category><category>observability</category><category>pixie</category><category>parca</category><category>cilium</category><category>hubble</category><category>tetragon</category><category>beyla</category><category>coroot</category><category>falco</category><category>opentelemetry</category><category>kubernetes</category><category>2026</category><category>deep-dive</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive</guid>
    <title>eBPF 관찰성 2026 — Pixie / Parca / Cilium Hubble / Tetragon / Beyla / Coroot / Falco 심층 가이드</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-15-ebpf-observability-2026-pixie-parca-cilium-hubble-tetragon-beyla-deep-dive</link>
    <description>2026년 시점의 eBPF 생태계를 한 번에 정리한다. Pixie, Parca, Cilium Hubble, Tetragon, BCC/bpftrace, OpenTelemetry eBPF Collector, Grafana Beyla, Coroot, Inspektor Gadget, Kepler, Falco 등 주요 도구를 비교하고, CO-RE 혁명과 Windows/macOS 이식까지 다룬다.</description>
    <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ebpf</category><category>observability</category><category>pixie</category><category>parca</category><category>cilium</category><category>hubble</category><category>tetragon</category><category>beyla</category><category>coroot</category><category>falco</category><category>opentelemetry</category><category>kubernetes</category><category>2026</category><category>deep-dive</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive.en</guid>
    <title>Distributed Tracing &amp; OpenTelemetry 2026 — OTel / Jaeger / Tempo / Zipkin / Honeycomb / Lightstep / SigNoz / SkyWalking / Datadog APM Deep Dive</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive.en</link>
    <description>In 2026, distributed tracing has converged on OpenTelemetry. The OTel spec and Collector, W3C Trace Context and B3 Propagation, OSS backends like Jaeger/Tempo/Zipkin, the observability 2.0 camp (Honeycomb, SigNoz), APM giants (Lightstep, Datadog, New Relic, Dynatrace), eBPF auto-instrumentation (Pixie, Beyla) — where to pick what, how to tame head vs tail sampling and cost, and how Korean and Japanese companies actually migrated.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>distributed-tracing</category><category>opentelemetry</category><category>otel</category><category>otelcol</category><category>jaeger</category><category>tempo</category><category>zipkin</category><category>honeycomb</category><category>charity-majors</category><category>lightstep</category><category>servicenow</category><category>signoz</category><category>apache-skywalking</category><category>datadog-apm</category><category>new-relic-apm</category><category>elastic-apm</category><category>sentry-performance</category><category>dynatrace</category><category>appdynamics</category><category>splunk</category><category>pixie</category><category>beyla</category><category>w3c-trace-context</category><category>b3-propagation</category><category>baggage</category><category>head-based-sampling</category><category>tail-based-sampling</category><category>2026</category><category>deep-dive</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive.ja</guid>
    <title>分散トレーシング &amp; OpenTelemetry 2026 — OTel / Jaeger / Tempo / Zipkin / Honeycomb / Lightstep / SigNoz / SkyWalking / Datadog APM 徹底比較</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive.ja</link>
    <description>2026年、分散トレーシングは OpenTelemetry に収束した。OTel 仕様と Collector、W3C Trace Context と B3 伝搬、Jaeger / Tempo / Zipkin といった OSS バックエンド、Honeycomb / SigNoz の observability 2.0 陣営、Lightstep と Datadog / New Relic / Dynatrace といった APM 巨人、Pixie / Beyla に代表される eBPF 自動計装まで — どこで何を選ぶか、ヘッド/テールサンプリングと費用をどう抑えるか、韓国・日本企業がどう移行したかを徹底比較する。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>distributed-tracing</category><category>opentelemetry</category><category>otel</category><category>otelcol</category><category>jaeger</category><category>tempo</category><category>zipkin</category><category>honeycomb</category><category>charity-majors</category><category>lightstep</category><category>servicenow</category><category>signoz</category><category>apache-skywalking</category><category>datadog-apm</category><category>new-relic-apm</category><category>elastic-apm</category><category>sentry-performance</category><category>dynatrace</category><category>appdynamics</category><category>splunk</category><category>pixie</category><category>beyla</category><category>w3c-trace-context</category><category>b3-propagation</category><category>baggage</category><category>head-based-sampling</category><category>tail-based-sampling</category><category>2026</category><category>deep-dive</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive</guid>
    <title>분산 추적 &amp; OpenTelemetry 2026 — OTel / Jaeger / Tempo / Zipkin / Honeycomb / Lightstep / SigNoz / SkyWalking / Datadog APM 심층 비교</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-distributed-tracing-opentelemetry-2026-otel-jaeger-tempo-zipkin-honeycomb-lightstep-signoz-skywalking-datadog-apm-deep-dive</link>
    <description>2026년 분산 추적은 OpenTelemetry로 수렴했다. OTel 사양과 Collector, W3C Trace Context와 B3 Propagation, Jaeger/Tempo/Zipkin 같은 OSS 백엔드, Honeycomb과 SigNoz 같은 observability 2.0 진영, Lightstep과 Datadog/New Relic/Dynatrace 같은 APM 거인, 그리고 Pixie/Beyla로 대표되는 eBPF 자동 계측까지 — 어디서 무엇을 골라야 하는지, 헤드/테일 샘플링과 비용은 어떻게 다스리는지, 한국과 일본 기업들이 어떻게 마이그레이션했는지까지 심층 비교.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>distributed-tracing</category><category>opentelemetry</category><category>otel</category><category>otelcol</category><category>jaeger</category><category>tempo</category><category>zipkin</category><category>honeycomb</category><category>charity-majors</category><category>lightstep</category><category>servicenow</category><category>signoz</category><category>apache-skywalking</category><category>datadog-apm</category><category>new-relic-apm</category><category>elastic-apm</category><category>sentry-performance</category><category>dynatrace</category><category>appdynamics</category><category>splunk</category><category>pixie</category><category>beyla</category><category>w3c-trace-context</category><category>b3-propagation</category><category>baggage</category><category>head-based-sampling</category><category>tail-based-sampling</category><category>2026</category><category>deep-dive</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive.en</guid>
    <title>Network &amp; Service Observability 2026 Deep Dive — eBPF · Cilium Hubble · Pixie · Pyroscope · Grafana Loki + Tempo + Mimir · Netdata · OpenTelemetry</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive.en</link>
    <description>In 2026, observability rests on four pillars (metrics, logs, traces, profiles) and eBPF auto-instrumentation is now the default. Cilium Hubble, Pixie, Pyroscope, the Grafana LGTM stack, Netdata, and OpenTelemetry — a single map of what to use, where, and at what cost. With real adoption stories from Korea (NCsoft, Coupang, Naver, Kakao) and Japan (Mercari, LINE Yahoo, CyberAgent).</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>ebpf</category><category>cilium-hubble</category><category>pixie</category><category>pyroscope</category><category>grafana-loki</category><category>grafana-tempo</category><category>netdata</category><category>opentelemetry</category><category>monitoring</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive.ja</guid>
    <title>ネットワーク &amp; サービスオブザーバビリティ 2026 完全ガイド — eBPF · Cilium Hubble · Pixie · Pyroscope · Grafana Loki + Tempo + Mimir · Netdata · OpenTelemetry 深掘り</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive.ja</link>
    <description>2026年のオブザーバビリティはメトリクス・ログ・トレース・プロファイルの4本柱と、eBPFによる自動計装が標準である。Cilium Hubble、Pixie、Pyroscope、Grafana LGTMスタック、Netdata、OpenTelemetryまで — 何をいくらでどこに使うかを一枚の地図にまとめる。韓国NCsoft、Coupang、Naver、Kakaoと日本Mercari、LINE Yahoo、CyberAgentの導入事例も含む。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>ebpf</category><category>cilium-hubble</category><category>pixie</category><category>pyroscope</category><category>grafana-loki</category><category>grafana-tempo</category><category>netdata</category><category>opentelemetry</category><category>monitoring</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive</guid>
    <title>네트워크 &amp; 서비스 옵저버빌리티 2026 완벽 가이드 - eBPF · Cilium Hubble · Pixie · Pyroscope · Grafana Loki + Tempo + Mimir · Netdata · OpenTelemetry 심층 분석</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-network-service-observability-2026-ebpf-cilium-hubble-pixie-pyroscope-grafana-loki-tempo-netdata-deep-dive</link>
    <description>2026년 옵저버빌리티는 메트릭·로그·트레이스·프로파일 4 기둥과 eBPF 자동 계측이 표준이다. Cilium Hubble, Pixie, Pyroscope, Grafana LGTM 스택, Netdata, OpenTelemetry까지 — 무엇을 어떤 비용에 어디서 쓸지 한 번에 정리한다. 한국 NCsoft, Coupang, Naver, Kakao와 일본 Mercari, LINE Yahoo, CyberAgent 도입 사례 포함.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>observability</category><category>ebpf</category><category>cilium-hubble</category><category>pixie</category><category>pyroscope</category><category>grafana-loki</category><category>grafana-tempo</category><category>netdata</category><category>opentelemetry</category><category>monitoring</category>
  </item>

    </channel>
  </rss>
