<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>distributed-system on Shylock Hg</title>
    <link>/tags/distributed-system/</link>
    <description>Recent content in distributed-system on Shylock Hg</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Dec 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/tags/distributed-system/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Distributed tracing</title>
      <link>/post/2019/12/10/distributed-tracing/</link>
      <pubDate>Tue, 10 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>/post/2019/12/10/distributed-tracing/</guid>
      <description>Overview The distributed tracing system like the perf in for process, the distributed tracing trace the RPC but perf trace the function calling.
Basic concepts  Trace, a whole RPC chain tracing, consist by spans (DAG structured) Span, a once RPC tracing Tow relationship inter span, ChildOf, FollowOf  Inter-Process To tracing inter process, we must record the relationship inter span. So the one method is to propagating the context of span with RPC calling as below:</description>
    </item>
    
  </channel>
</rss>