Marc Pichler

I'm still somewhat confused about this situation and have not had much time to look into this. I'll try to find someone who has more context to look into this....

Hi @s0, I'm not sure I fully understand the use-case > and I would like access to additional information about user request when handling data requests Does this mean that...

@s0 thank you for your reply. Unfortunately I think this use-case is outside the scope of this project (it is a very cool one, though!). OpenTelemetry is designed in a...

Hi @lionskape - thanks for reaching out. I looked into it and this is indeed a bug in this unreleased feature that has a few more layers to this bug...

Closing this as we now have a permanent feature-freeze for the 1.x-line of packages. A summary of how we will move forward: - Any experimental packages that jump to stable...

Something that came up on #5217: I think we should have code-only stability-opt-in config, as opposed to pseudo-env var config via `window` for the xhr/fetch instrumentation.

I went through the code, and I think we can apply all of the above proposals. The hardest one to do might be > - remove asyncAttributesPending and waitForAsyncAttributes. Make...

@seemk hmm, from what I understand this is what this issue in spirit is about. [ `IResource.attributes`](https://github.com/open-telemetry/opentelemetry-js/blob/c9b5bb0bfeb77ab9ce238fc28b505daa87ed419e/packages/opentelemetry-resources/src/IResource.ts#L36) becomes `IResource.getAttributes()` that is `async` - it's only intended to be awaited by...

FWIW it's already possible to do so when using the `@opentelemetry/instrumenation-http` package in conjunction with `@opentelemetry/instrumentation-express` for instance. what that instrumentation does is this: ```ts const rpcMetadata = getRPCMetadata(context.active()); //...

@ethanmick [as I said earlier, this is already possible](https://github.com/open-telemetry/opentelemetry-js/issues/4890#issuecomment-2377348854). You can do it on the request hook, or even if the span is currently active while handling your request in...