ClockSkew adjuster modifies original spans when using the InMemory storage backend

[zachidan]

When using the InMemory storage backend, the ClockSkew adjuster modifies the start time and log timestamps of the original spans that are stored in the InMemory storage backaned.

As a result, once the ClockSkew adjuster was executed, there is no way to get the unadjusted spans from the InMemory storage backend. Although the InMemory storage backend should be used only for development, it is useful to get the unadjusted spans from this storage backend.

[bdelbosc]

Hi, I have incoherent span timestamp when using child_of relation,
in the case of asynchronous processing the parent span has no overlap with the child,
but Jaeger renders the trace like if the child span was in the middle of the parent span (instead of being after).
I am using the in-memory version of Jaeger, is this the same problem due to the ClockSkew adjuster or is this because my relation should be defined as followsFrom ?

[yurishkuro]

For async you should be using follows-from reference.

[bdelbosc]

Thanks for your reply, I will try to figure out how to do that with opencensus.

[yurishkuro]

oh, I don't think you can.

[bdelbosc]

Apparently, I found a way to use follows-from reference with opencensus-java:
census-instrumentation/opencensus-java#1760 (comment)

[jkowall]

This is handled in Otel now, so closing it out.