start_time and end_time getting cut from microsecond precision to millisecond precision in xray exporter

[abalasky-chronos]

Hey all! I'm using the AWS Otel collector to export my Java SDK Otel traces to the Xray backend. I notice that the start_time and end_time of the converted segment get recorded to millisecond precision (e.g. 2023-05-23 18:00:33.856 (UTC)) in the Xray frontend causing many of my subsegments to register as 0ms.

However when using a local Tempo (Grafana tracing backend for Otel) im able to see that the precision of StartTime and EndTime is in the micros which results in my span durations being displayed correct.

I see that the Otel span to Xray segment conversion for StarTime and EndTime happens here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/awsxrayexporter/internal/translator/segment.go#L94. Is this perhaps dropping the microsecond precision? Has anyone encountered this where there micro second segments are showing up as 0ms in XRay UI?

I would love to be able to use XRay to see the performance of these microsecond duration segments.