Routing Traces to Multiple Backends & Custom Routing Connector Issues

[NarendraN-kore]

Hi,

I'm trying to route traces to multiple backends (e.g., sending some traces to a Signoz instance and others to Dynatrace based on accountId).

Flow of Tracing Setup:
Backend Service: Generates traces with span attributes (including accountId).
Otel Agent (Collector): Receives trace data and applies routing logic.
Trace Routing:
If accountId belongs to Tenant A, send the trace to Signoz.
If accountId belongs to Tenant B, send the trace to Dynatrace.
Issue & Queries:
I was using OpenTelemetry version 0.88, where I leveraged the routing connector. However, the routing statement could only access resource attributes for querying. Since the Node Trace SDK is singleton and its resource attributes cannot be modified dynamically, I attempted to build a custom routing connector that could access span attributes for routing. However, this approach is causing trace data loss.

I tried upgrading to the latest OpenTelemetry release, but it appears that the routing connector has been deprecated.

I have the following queries:

How can I route traces to multiple backends dynamically?
How can I resolve trace data loss in my custom routing connector?
Since the latest OpenTelemetry release does not include a routing connector, what is the recommended alternative approach?
Looking forward to guidance on this. Thanks!