Skip to content

the invocation chain is break when using service invoke #2504

Description

@keranbingaa

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

Ask your question here

When I use server invocation in dapr,I find the invocation chain is break(I use zipkin as trace tool).
For example,client A calls server B,and B calls C in the server implement. The invocation chain should be A ->B->C, but there will be two chains in zipkin:A->B and B->C.
I tried go sdk and java sdk, and the result is same. Must I deliver trace information in server implement to construct invokcation chain?

Metadata

Metadata

Assignees

Labels

P1kind/observabilityDapr observability relatedquestionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions