http-transport-utils logs success as error

[mattfysh]

opentelemetry-js/experimental/packages/otlp-exporter-base/src/transport/http-transport-utils.ts

Lines 102 to 108 in 0ae25f1

	const reportTimeoutErrorEvent = nodeVersion >= 14 ? 'close' : 'abort';
	req.on(reportTimeoutErrorEvent, () => {
	onDone({
	status: 'failure',
	error: new Error('Request timed out'),
	});
	});

Log line:

{
   "message":"Request timed out",
   "originalLine":"59",
   "originalColumn":"25",
   "line":"87",
   "column":"24",
   "sourceURL":"/bun/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js",
   "stack":"@see below",
   "name":"Error"
}

Stack:

Error: Request timed out
    at <anonymous> (/bun/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:87:24)

[pichlermarc]

This seems to be a duplicate of #5260
Seems to be due to a difference in Node.js and Bun's implementations of the 'http' module.

[pichlermarc]

Regardless of that, I think it is true that we should not use the close event like this. It would probably also cause the callback to be called even if a success response has been received already. Fixes would be appreciated.