Node.js: span.end(timestamp) requires millisecond epoch #18697
Description
Description
When creating spans via startSpan, startManualSpan, etc, startTime is in seconds since epoch but on Node.js, span.end(timestamp) expects a millisecond epoch. Using mixed timestamp units is very confusing and I lost a couple of hours to this! The jsdocs for all timestamp based arguments are not clear what kind of timestamp should be used.
As far as I can tell, this impacts all SDKs using Open Telemetry and so means the SDKs actually differ over what kind of timestamp they support. The browser SDKs support either second or millisecond epochs.