This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch zipkin-trace
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git
The following commit(s) were added to refs/heads/zipkin-trace by this push:
new 49be8c6 Make the description more clear.
new 8142033 Merge branch 'zipkin-trace' of
https://github.com/apache/incubator-skywalking into zipkin-trace
49be8c6 is described below
commit 49be8c61072b7898f0d59083d0f102845cc91262
Author: Wu Sheng <[email protected]>
AuthorDate: Fri Mar 29 08:58:14 2019 -0700
Make the description more clear.
---
docs/en/setup/backend/backend-receivers.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/docs/en/setup/backend/backend-receivers.md
b/docs/en/setup/backend/backend-receivers.md
index c54b94b..a4302a9 100644
--- a/docs/en/setup/backend/backend-receivers.md
+++ b/docs/en/setup/backend/backend-receivers.md
@@ -62,13 +62,15 @@ because gRPC/HTTP servers of core are still used for UI and
OAP internal communi
## Zipkin receiver
Zipkin receiver could work in two different mode.
-1. Tracing mode(default). Tracing mode is that, skywalking OAP acts like
zipkin collector, which provide persistence and query,
-but wouldn't analysis metric from them. In most case, I suggest you could use
this feature, when metric come from service mesh.
-Also, in this mode, Zipkin receiver requires `zipkin-elasticsearch` storage
implementation active.
+1. Tracing mode(default). Tracing mode is that, skywalking OAP acts like
zipkin collector,
+fully supports Zipkin v1/v2 formats through HTTP service,
+also provide persistence and query in skywalking UI.
+But it wouldn't analysis metric from them. In most case, I suggest you could
use this feature, when metrics come from service mesh.
+Notice, in this mode, Zipkin receiver requires `zipkin-elasticsearch` storage
implementation active.
Read [this](backend-storage.md#elasticsearch-6-with-zipkin-trace-extension) to
know
how to active.
1. Analysis mode(Not production ready), receive Zipkin v1/v2 formats through
HTTP service. Transform the trace to skywalking
-native format, and analysis like skywalking trace. This feature can't work in
production env, and
+native format, and analysis like skywalking trace. This feature can't work in
production env right now,
because of Zipkin tag/endpoint value unpredictable, we can't make sure it fits
production env requirements.
Active `analysis mode`, you should set `needAnalysis` config.
