IssueTracker

We have multiple services deployed in Cloud Run that are each instrumented for Distributed Tracing. We have a enterprise solution for distributed tracing where we are sending our traces (not Cloud Trace), since Cloud Run adds a new span with Cloud Trace to the traceparent level we loose connections between spans in the central location.

Example:
Given the following components:
A - External Caller (not in GCP)
B - API Gateway (not in GCP)
C - Global Load Balancer
D - Cloud Run (1) Service in our project
E - Internal Load Balancer
F - Cloud Run (2) Service in our project

The following sequence of events happens:
A - creates the trace (first span) when calling B
B - creates a span to cover the request from the gateway perspective when calling C
C - calls D
D - sees the span created by cloud run not the span from B - this causes a data gap and looses the span connection, creates a client span to call E
E - calls F
 F - sees the span created by cloud run, not the span from D - this causes a data gap and looses the span connection

We have explored the possibility of exporting Cloud Trace to our internal tracing service, however that is limited per docs to the 10 rps tracing limit, so we are not able to export each span.