opentelemetry-cloud-trace-exporter does not stack trace through multiple cloud run services

[sytdas]

Please answer these questions before submitting a bug report.

What version of OpenTelemetry are you using?

1.4.1

What version of Node are you using?

18

What did you do?

I set up a sample repo, service-one receives request then send it to service-two
https://github.com/sytdas/tracejs

What did you expect to see?

The trace includes service-one and service-two

What did you see instead?

Cloud trace shows trace for service-one and service-two separately

Additional context

Add any other context about the problem here.

[aabmass]

For the Jaeger screenshot, were the applications running in Cloud Run or locally? This looks like a propagation issue and the exporter shouldn't affect this.

[sytdas]

@aabmass The first picture is applications run on my localhost. 2nd and 3rd pictures of deployed app on cloud run and its trace.

[sytdas]

I found that Cloud Trace use different header than opentelemetry. 😞

"x-cloud-trace-context: 49f0d6a0b5ae486cf56c936167a8fdc1/7488432643372146419;o=1"
"traceparent: 00-49f0d6a0b5ae486cf56c936167a8fdc1-67ec41d050a2def3-01"