moves from @opentelemetry/exporter-trace-otlp-http -> `@opentelemet…

…ry/exporter-trace-otlp-proto` for protobuf support; our existing infrastructure uses VictoriaMetrics, which only supports protobuf encoding, whereas `@opentelemetry/exporter-trace-otlp-http` seems to only support json encoding

apps/cdd-backend/src/config/telemetry.ts

@@ -2,7 +2,7 @@
 
 import os from 'node:os';
 import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
-import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
+import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-proto';
 import { Resource } from '@opentelemetry/resources';
 import { NodeSDK } from '@opentelemetry/sdk-node';
 import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions';
@@ -26,7 +26,7 @@ const telemetryEnvConfig = (): TelemetryConfig | undefined => {
     hostname: process.env.OTLP_HOSTNAME,
     service: process.env.OTLP_SERVICE,
   };
-  
+
 
   if (rawConfig.url) {
     return telemetryZ.parse(rawConfig);

package.json

@@ -83,7 +83,7 @@
     "@nestjs/swagger": "^6.2.1",
     "@opentelemetry/api": "^1.4.0",
     "@opentelemetry/auto-instrumentations-node": "^0.36.4",
-    "@opentelemetry/exporter-trace-otlp-http": "^0.35.1",
+    "@opentelemetry/exporter-trace-otlp-proto": "^0.47.0",
     "@opentelemetry/resources": "^1.9.1",
     "@opentelemetry/sdk-node": "^0.35.1",
     "@opentelemetry/semantic-conventions": "^1.9.1",