feat: fetch OpenTelemetry configuration at runtime for dynamic client setup

Author: nicosammito

src/instrumentation-client.ts

@@ -1,11 +1,17 @@
 import "@opentelemetry/api-logs"
-import initializeLogs, {openTelemetryClientLogsProvider} from "@core/util/open-telemetry-logs"
-import initializeTraces, {openTelemetryClientTracesProvider} from "@core/util/open-telemetry-traces"
-import {logs} from "@opentelemetry/api-logs"
-import {trace} from "@opentelemetry/api"
+import {ClientOtelConfig} from "@core/util/open-telemetry"
+import {initializeClientLogs} from "@core/util/open-telemetry-logs"
+import {initializeClientTraces} from "@core/util/open-telemetry-traces"
 
-initializeLogs("client")
-if (openTelemetryClientLogsProvider) logs.setGlobalLoggerProvider(openTelemetryClientLogsProvider)
-
-initializeTraces("client")
-if (openTelemetryClientTracesProvider) trace.setGlobalTracerProvider(openTelemetryClientTracesProvider)
+// The browser OpenTelemetry configuration is fetched from the server at runtime
+// (see /api/config) instead of relying on build-time inlined NEXT_PUBLIC_*
+// variables, so the collector endpoints can be changed without rebuilding.
+fetch("/api/config")
+    .then((response) => response.json())
+    .then((config: ClientOtelConfig) => {
+        initializeClientLogs(config)
+        initializeClientTraces(config)
+    })
+    .catch(() => {
+        // Telemetry is best-effort; ignore config fetch/initialization failures.
+    })