Feature Request: Multiple Export Endpoints for Traces

Problem

The Traces export UI only allows a single endpoint URL + auth header set. Customers whose observability infrastructure is separated by region need to send exported spans to a different endpoint per region, which isn't possible natively today.

Workaround (confirmed working)

Point Checkly's trace export at a self-hosted OpenTelemetry Collector, then configure multiple destinations downstream — multiple exporters for duplication, or a routing connector keyed off a region attribute for true per-region routing. This works but requires customers to run and maintain extra collector infrastructure.

Proposed Solution

Native support in the Traces export config for multiple endpoints, ideally with region- (or attribute-) based routing so spans reach the correct destination rather than being duplicated to all. A simpler v1 could support multiple endpoints with duplication; attribute-based routing is the higher-value version.

Impact

Removes the need for region-separated customers to run their own collector just for fan-out/routing, and lowers the barrier to adopting trace export for enterprise customers with multi-region observability stacks.