[GitHub] [incubator-skywalking] wu-sheng commented on a change in pull request #2424: Support Backend acts as pure Zipkin collector

[GitBox <gi...@apache.org>]

wu-sheng commented on a change in pull request #2424: Support Backend acts as pure Zipkin collector
URL: https://github.com/apache/incubator-skywalking/pull/2424#discussion_r270474220
 
 

 ##########
 File path: docs/en/setup/backend/backend-receivers.md
 ##########
 @@ -59,4 +58,25 @@ receiver-sharing-server:
 ```
 
 Notice, if you add these settings, make sure they are not as same as core module,
-because gRPC/HTTP servers of core are still used for UI and OAP internal communications.
\ No newline at end of file
+because gRPC/HTTP servers of core are still used for UI and OAP internal communications.
+
+## 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,
 
 Review comment:
   Please review the new description again.
   
   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.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services