Gerhard Stöbich

Seems like browser tests are unhappy: ``` ERROR in ./test/common/anchored-clock.test.ts Module not found: Error: Can't resolve 'perf_hooks' in '/__w/opentelemetry-js/opentelemetry-js/packages/opentelemetry-core/test/common' @ ./test/common/anchored-clock.test.ts 19:21-42 ```

At least instrumentation express provides a timestamp to `span.end()` but not to `startSpan()`. Therefore two different time sources are used resulting in undefined results. See https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1209 and https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1193

Seems like this is inconsistent across techs. [Java doesn't use lowercase keys.](https://github.com/open-telemetry/opentelemetry-java/blob/91bd17e09b38aff11f07da21d9eeb65aa4764a15/extensions/trace-propagators/src/main/java/io/opentelemetry/extension/trace/propagation/B3Propagator.java#L50-L53). I think the OTel spec should clarify here to avoid interoperability issues like this.

I agree that docs should be updated to point users to `AsyncLocalStorage`. I doubt diagnostics channel as a replacement for async_hooks users, maybe in some rare case. I don't agree...

I will be also not there. I haven't even noticed that there is a summit and a diagnostics session... Seems I monitor the wrong channels/repos.

I fear that agreeing on traceId/spanId across different vendors/tools wont work in general. One tool might group two requests on one trace wheres the other prefers separate traces. As a...

@dyladan Even it's assigned to you I created a simple PR to improve this: #3502

If it is about any js runtime the node.js specific parts should be removed/renamed/... * anything coming from v8 is not automatically applicable to js engine in firefox or safari...

There are JS engines (e.g. quickjs) which use a different heap structure/gc then google v8 (the JS engine used by node.js or deno). The proposed gc/heap metrics match fine to...

As long as quite some log related packages (as of now all) are experimental and in the 0.x.y version range release here and dependency update by consumers need to go...