CODEWITHSUNDEEP
javascriptjavamicroservicesjaegeropentracing
cyber_trunk
cyber_trunk

Reputation: 129

Jaeger traces out of order

I have a front-end application (component A) that makes a request to a Java back-end application (component B).

Both components are configured to export trace information to my jaegertracing/all-in-one:1.37 deployment.

The headers from component A are propagating correctly to component B, and I can see the traces being nested, but they are out of order.enter image description here enter image description here

I printed the start and end time for both component A and B, it looks like timestamp from component B is earlier than of component A. Has anyone run into this issue before?

The way I print the epoch time for both services are:

Java System.currentTimeMillis();

JavaScript new Date().getTime()

Upvotes: 1

Views: 611

Answers (1)

cyber_trunk
cyber_trunk

Reputation: 129

Jaeger has a solution to address the possibility of clock skew between the many host machines part of the traces: https://www.jaegertracing.io/docs/1.21/deployment/#clock-skew-adjustment

It is most likely the case that one of the host machines have a clock skew which causes the tracing to be out of order.

Upvotes: 1

Related Questions