Why is the "span startTime" that I queried from es and JaegerUI query different?

[code98]

Why is the "span startTime" that I queried from es and JaegerUI query different?

Same traceId
Same SpanId
Same Elasticsearch

Data in the ES

JaegerUi, use this interface "/api/traces"

[yurishkuro]

Possibly due to clock skew adjustment. Try with ?raw=true parameter

[code98]

Possibly due to clock skew adjustment. Try with ?raw=true parameter

Not a time zone issue, because it is a few milliseconds

[yurishkuro]

Clock skew adjustment is not related to time zone, it's the small differences in system clocks on different servers due to clock drift. Jaeger query service, by default, attempts to correct for these differences. By adding ?raw=true parameter to the query you instruct it not to apply this adjustment.

[code98]

Clock skew adjustment is not related to time zone, it's the small differences in system clocks on different servers due to clock drift. Jaeger query service, by default, attempts to correct for these differences. By adding ?raw=true parameter to the query you instruct it not to apply this adjustment.

Hello, I still don't understand what it means here. I want to query the span data in Elasticsearch. If I don't make clock adjustments, is startTime accurate? Are all spans linear based on startTime? thank you!

[yurishkuro]

for example: /api/traces/665010a93ef2ee1f?raw=true&prettyPrint=true

[code98]

Clock skew adjustment is not related to time zone, it's the small differences in system clocks on different servers due to clock drift. Jaeger query service, by default, attempts to correct for these differences. By adding ?raw=true parameter to the query you instruct it not to apply this adjustment.

The span data I queried from Elasticsearch can be used directly on my business system without making adjustments.

[yurishkuro]

do you still have a question?