Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

[Jaeger Tracing] Undesired Tracing Span Graph in NCM #711

Open
zzxgzgz opened this issue Dec 6, 2021 · 0 comments
Open

[Jaeger Tracing] Undesired Tracing Span Graph in NCM #711

zzxgzgz opened this issue Dec 6, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@zzxgzgz
Copy link
Contributor

zzxgzgz commented Dec 6, 2021

What happend:

  • With Jaeger Tracing added to the NCM in this PR, we found that the tracing graphs is not what we wanted, please refer to the graph below:

    the alcor.schema.GoalStateProvisioner/RequestGoalStates spans should be at the same level, rather than one being the child of the previous one.

We suspect that it has to do with this issue, we should try to implement the solution proposed in this issue as a solution. Another solution we can think of is replaceing the opentracing libraries with the opentelemetry libraries, the detail of which can be found in this issue

@zzxgzgz zzxgzgz added the enhancement New feature or request label Dec 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant