IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish: Being able to set up Trace spans from a different project. As with Metrics, customers would like to explore trace spans by gathering them from their desired projects and centralizing all of them from a scoping project. This is already possible with Metrics Scope, but currently there is no equivalent for Trace.

How this might work: Until now, discussions comment ‘similarly to Metrics Scope’.

If applicable, reasons why alternative solutions are not sufficient: At the moment there is a workaround consisting in writing double-spans, one to the application project and other in the central monitoring. However this will generate double of calls and therefore double Billing charges. Moreover, this would require building exporters for every project. Existing workarounds for 1st party spans aren't great: it would require polling reads to copy data into another project, and read quota is generally pretty limited, so is not suitable for frequent polling.

Other information (workarounds you have tried, documentation consulted, etc):

This impacts users on their observability workflow, API calls to retrieve traces from other projects fail and default to the current project, where the requested trace does not exist and returns an error.