Martin Kuba

@Flarna > If only for browsers it should be likely at WebSDK or in web specific instrumentations. The use cases I am aware of are for client applications. They are...

In JavaScript, we recently moved the X-Ray propagator from the contrib repository to the core repository, only realizing afterward that this constraint existed in the specification. The move was made...

@fuaiyi Apologies again for the delayed response. There are still ongoing discussions about what the Events API should look like (see https://github.com/open-telemetry/opentelemetry-specification/issues/3086). We discussed this in the Client Instrumentation SIG...

Thank you everyone for your comments. I have moved this back to draft, as it is not clear that this is necessarily the right direction. I have summarized the current...

The behavior is intended to generate spans only for events that have handlers in the application code. The handlers in application code will generally invoke other work (e.g. HTTP requests),...

This applies to the InstrumentationScope context that is applicable to spans, metrics, and logs. I think https://github.com/open-telemetry/opentelemetry-js/issues/4365 is specific to metrics.