[
https://issues.apache.org/jira/browse/SCB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317940#comment-16317940
]
ASF GitHub Bot commented on SCB-176:
------------------------------------
yhs0092 commented on issue #485: [SCB-176] Generate traceId
URL:
https://github.com/apache/incubator-servicecomb-java-chassis/pull/485#issuecomment-356206290
I've taken an exam on the situation when users enable our
ZipkinTracingHandler to use open zipkin.
In current solution, the traceId generated by TracingFilter will be ignored
by the inner logic of Brave, and a new span will be generated. The traceId
transported in the invocation chain is the one that Brave generates. And the
function of zipkin tracing works normally.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Generate TraceId not depending on trace/access mechanism
> --------------------------------------------------------
>
> Key: SCB-176
> URL: https://issues.apache.org/jira/browse/SCB-176
> Project: Apache ServiceComb
> Issue Type: Sub-task
> Components: Java-Chassis
> Reporter: YaoHaishi
> Assignee: YaoHaishi
> Priority: Minor
> Fix For: java-chassis-1.0.0-m1
>
>
> Generate traceId and transport it in invocation context.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
