Allow for ending Traces on a remote server

[solatis]

Please answer these questions before submitting a bug report.

What version of OpenCensus are you using?

1.5

What JVM are you using (java -version)?

Java8

What did you do?

We are using a CSP-style message passing framework framework, and I would like to implement my Trace in such a way that I can close a Trace on a remote server. With the current implementation, I can correlate all Spans under a single Trace and message the processing time of the individual steps, but the measurements for end-to-end latency seem to get lost.

To illustrate, this is what my traces currently look like:

Even though end-to-end latency is about 170ms, this fact appears to get lost in the overall trace. I believe being able to close the Trace / RootSpan on the last server would be a solution to this.

[bogdandrutu]

@solatis thanks for filing this bug/feature request. If you don't mind I would like to ask you about the infrastructure that you have here, do you have something like this: Service A -> queue -> Service B -> queue -> Service C? Or what is the overall architecture that you have?

We don't want to have a Span shared between different process because that implies the backends should support injecting partial Spans which not all of the backends accept.

Before jumping to proposals I would like to understand the overall workflow then I can propose something.

PS: Sorry for responding after 1.5months.

[endink]

+1 need