Marc Pichler

fix(instrumentation-http): add server attributes after they become available

1

## Which problem is this PR solving? While reviewing #5079 I noticed that we don't set `http.route` and `http.response.status` code in the server duration metrics, so this PR addresses a...

chore: move xray and xray-lambda propagators to contrib

2

## Which problem is this PR solving? - the spec prohibits us from hosting vendor propagators in the core repo. From the [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/6672dbc97ddeb34f36c020a0f0a30323c8bc4d95/specification/context/api-propagators.md?plain=1#L354-L356): > Additional `Propagator`s implementing vendor-specific protocols such...

## Description > [!IMPORTANT] > **The existence of this issue does not reflect the wish of the author for this to be implemented** > This is a feature request that...

## Description Any announcements/guidelines regarding breaking changes (for instance changes to language or runtime support) for `README.md` will go into into `README_NEXT.md`. They will remain there until we're ready to...

## Description > [!IMPORTANT] > This is currently on hold as it is not a focus topic for the SIG - do NOT open PRs. This issue will be updated...

[instrumentation-http] add hook for custom server and client metrics attributes

2

## Description > [!WARNING] > **The two issues linked below (#4095, #4096) are REQUIRED to be finished before implementation of this feature can start. Any PR opened to add this...

[sdk-logs] remove deprecated `LoggerProvider#addLogRecordProcessor()`

2

# Description To align with the other SDKs (`@opentelemetry/sdk-trace-*`, `@opentelemetry/sdk-metrics`) we should drop `LoggerProvider#addLogRecordProcessor()` in favor of the constructor option introduced in #5588 (issue #5559) **This issue is considered done...

[otlp-transformer] introduce separate entry-points for OTLP serializers

3

## Description In preparation of marking `@opentelemetry/otlp-transformer` as stable (#4582) we should introduce separate entry-points to ensure that - `@experimental` types/functions don't become part of the stable interface - use...

feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers

3

## Which problem is this PR solving? This is the second-to-last breaking PR for `@opentelemetry/otlp-transformer` before marking the package as stable (#4582). This solves some issues with rollup, that warns...

[otlp-transformer] rethink depending on all signal SDKs for OTLP transformation

1

Currently, we depend on all signals in the `@opentelemetry/otlp-transformer` package. We should find a way to either eliminate these dependencies or split the package up so that each signal transformation...