You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2019/03/15 08:46:12 UTC

[incubator-skywalking] branch wu-sheng-patch-1 created (now f68047c)

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch wu-sheng-patch-1
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git.


      at f68047c  Update Trace-Data-Protocol-v2.md

This branch includes the following new commits:

     new f68047c  Update Trace-Data-Protocol-v2.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[incubator-skywalking] 01/01: Update Trace-Data-Protocol-v2.md

Posted by wu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch wu-sheng-patch-1
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git

commit f68047c392c274bfa4842716775d07c9ac2e8ea8
Author: 吴晟 Wu Sheng <wu...@foxmail.com>
AuthorDate: Fri Mar 15 16:46:04 2019 +0800

    Update Trace-Data-Protocol-v2.md
---
 docs/en/protocols/Trace-Data-Protocol-v2.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/en/protocols/Trace-Data-Protocol-v2.md b/docs/en/protocols/Trace-Data-Protocol-v2.md
index 6b6481b..8e6ef25 100644
--- a/docs/en/protocols/Trace-Data-Protocol-v2.md
+++ b/docs/en/protocols/Trace-Data-Protocol-v2.md
@@ -47,9 +47,9 @@ e.g. accessing DB by JDBC, reading Redis/Memcached are cataloged an ExitSpan.
 
 3. Span parent info called Reference, which is included in span. Reference carries more fields besides 
 trace id, parent segment id, span id. Others are **entry service instance id**, **parent service instance id**,
-**entry endpoint**, **parent endpoint** and **network address**. Follow [SkyWalking Trace Data Protocol v2](Trace-Data-Protocol-v2.md),
+**entry endpoint**, **parent endpoint** and **network address**. Follow [Cross Process Propagation Headers Protocol v2](Skywalking-Cross-Process-Propagation-Headers-Protocol-v2.md),
 you will know how to get all these fields.
 
 ### Step 3. Keep alive.
 `ServiceInstancePing#doPing` should be called per several seconds. Make the backend know this instance is still
-alive. Existed **service instance id** and **UUID** used in `doServiceInstanceRegister` are required.
\ No newline at end of file
+alive. Existed **service instance id** and **UUID** used in `doServiceInstanceRegister` are required.