telemetry: emit socket_timeout in seconds to match receiver proto

The driver tracks socketTimeout in milliseconds, but the receiver proto
field socket_timeout is defined in seconds. Convert ms -> s at export so a
15-minute timeout reports as 900s instead of 900000s. Adds regression tests
covering the default value and sub-second rounding.

Co-authored-by: Isaac

Author: samikshya-db

lib/telemetry/DatabricksTelemetryExporter.ts

@@ -417,7 +417,13 @@ export default class DatabricksTelemetryExporter {
           use_proxy: metric.driverConfig.useProxy,
           enable_arrow: metric.driverConfig.arrowEnabled,
           enable_direct_results: metric.driverConfig.directResultsEnabled,
-          socket_timeout: metric.driverConfig.socketTimeout,
+          // The proto `socket_timeout` field is defined in seconds, but the driver
+          // tracks socketTimeout in milliseconds — convert so the receiver records
+          // the correct unit (e.g. 900000ms -> 900s) instead of treating ms as seconds.
+          socket_timeout:
+            typeof metric.driverConfig.socketTimeout === 'number'
+              ? Math.round(metric.driverConfig.socketTimeout / 1000)
+              : metric.driverConfig.socketTimeout,
           enable_metric_view_metadata: metric.driverConfig.enableMetricViewMetadata,
         };
       }

tests/unit/telemetry/DatabricksTelemetryExporter.test.ts

@@ -162,6 +162,51 @@ describe('DatabricksTelemetryExporter', () => {
     });
   });
 
+  describe('export() - driver_connection_params', () => {
+    // The driver tracks socketTimeout in milliseconds, but the receiver proto
+    // defines `socket_timeout` in seconds. Lock in the ms -> s conversion so a
+    // 15-minute (900000ms) timeout is reported as 900s, not 900000s.
+    function getConnectionParams(sendRequestStub: sinon.SinonStub): any {
+      const init = sendRequestStub.firstCall.args[1] as { body: string };
+      const body = JSON.parse(init.body);
+      const log = JSON.parse(body.protoLogs[0]);
+      return log.entry.sql_driver_log.driver_connection_params;
+    }
+
+    function makeConnectionMetric(socketTimeout: number): TelemetryMetric {
+      return makeMetric({
+        metricType: 'connection',
+        driverConfig: {
+          driverName: 'nodejs-sql-driver',
+          driverVersion: '1.14.0',
+          socketTimeout,
+        } as any,
+      });
+    }
+
+    it('converts socketTimeout from milliseconds to seconds', async () => {
+      const context = new ClientContextStub({ telemetryAuthenticatedExport: true } as any);
+      const registry = new CircuitBreakerRegistry(context);
+      const exporter = new DatabricksTelemetryExporter(context, 'host.example.com', registry, fakeAuthProvider);
+      const sendRequestStub = sinon.stub(exporter as any, 'sendRequest').returns(makeOkResponse());
+
+      await exporter.export([makeConnectionMetric(900000)]);
+
+      expect(getConnectionParams(sendRequestStub).socket_timeout).to.equal(900);
+    });
+
+    it('rounds sub-second socketTimeout values', async () => {
+      const context = new ClientContextStub({ telemetryAuthenticatedExport: true } as any);
+      const registry = new CircuitBreakerRegistry(context);
+      const exporter = new DatabricksTelemetryExporter(context, 'host.example.com', registry, fakeAuthProvider);
+      const sendRequestStub = sinon.stub(exporter as any, 'sendRequest').returns(makeOkResponse());
+
+      await exporter.export([makeConnectionMetric(1500)]);
+
+      expect(getConnectionParams(sendRequestStub).socket_timeout).to.equal(2);
+    });
+  });
+
   describe('export() - retry logic', () => {
     it('should retry on retryable HTTP errors (503)', async () => {
       const context = new ClientContextStub({ telemetryMaxRetries: 2 } as any);