Support per-signal OTLP exporter endpoints in hyperdx/browser

[vinzee]

Summary

Add optional tracesUrl and logsUrl config options to @hyperdx/browser's init(),
allowing independent configuration of trace and log export endpoints.

This is useful for complex networking environments or when routing different
telemetry signals to different backends (e.g. traces to one collector, session
replay logs to another).

Changes

• Added optional tracesUrl and logsUrl fields to BrowserSDKConfig
• When provided, these are used as-is for the Rum (traces) and SessionRecorder (logs)
  OTLP exporters respectively
• When omitted, the existing behavior is preserved: ${url}/v1/traces and ${url}/v1/logs

Usage

HyperDX.init({
  apiKey: '...',
  service: 'my-app',
  url: 'https://collector.example.com',                // base URL (existing behavior)
  tracesUrl: 'https://traces.example.com/v1/traces',   // optional override
  logsUrl: 'https://logs.example.com/v1/logs',         // optional override
});

Context

• Related issue: [Feature request] Support per signal OTLP endpoints for hyperdx-frontend's internal telemetry signals hyperdx#2076
• Related PR: Support per-signal OTLP exporter endpoints for Hyperdx internal telemetry hyperdx#2098

[changeset-bot]

🦋 Changeset detected

Latest commit: e1b1508

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hyperdx/browser	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vinzee]

Related:

• Issue: [Feature request] Support per signal OTLP endpoints for hyperdx-frontend's internal telemetry signals hyperdx#2076
• Companion PR (hyperdx repo): Support per-signal OTLP exporter endpoints for Hyperdx internal telemetry hyperdx#2098

[karl-power]

LGTM @vinzee! Can you add a changeset please? yarn changeset from repo root. Thanks!

[vinzee]

@karl-power added the changeset