Marc Pichler
Marc Pichler
I backported bugfixes to keep the 2-week release schedule in #4682. This PR carries over the version bumps and changelog adjustments.
## Which problem is this PR solving? Adds a few more script for release-automation that I usually did by hand. Moving us closer to having a fully-automated solution. This adds:...
In `@opentelemetry/instrumentation` we test `RequireInTheMiddleSingleton` by using the `cpx2` package. https://github.com/open-telemetry/opentelemetry-js/blob/63d74cdc366fc337be66c1a766a2cc8e5275a85a/experimental/packages/opentelemetry-instrumentation/test/node/RequireInTheMiddleSingleton.test.ts#L42-L43 As we don't use the `cpx2` package anywhere else anymore, having a local test package would help us get...
## API 1.9.0 ### :rocket: (Enhancement) * feat(api): allow adding span links after span creation [#4536](https://github.com/open-telemetry/opentelemetry-js/pull/4536) @seemk * This change is non-breaking for end-users, but breaking for Trace SDK implementations...
Currently, we don't auto-configure a `MetricReader`/exporter combination when using the `@opentelemetry/sdk-node` package. Goal of this issue is to implement exporter selection for metrics based on this specification: - https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#exporter-selection **For...
The `@opentelemetry/instrumentation` package exports a `InstrumentationOption` type: ```ts export type InstrumentationOption = | typeof InstrumentationBase | (typeof InstrumentationBase)[] | Instrumentation | Instrumentation[]; ``` However, `InstrumentationBase` implements `Instrumentation` already. Further, this...
## Which problem is this PR solving? This is based on @clintonb's work on adding a `createGauge()` API. We did not have a way to introduce experimental API features for...
**Description** Currently we always merge `Resource.default()` with the constructor-provided resource. However, the [spec states that](https://github.com/open-telemetry/opentelemetry-specification/blob/f3511a5ccda376dfd1de76dfa086fc9b35b54757/specification/resource/sdk.md?plain=1#L33C1-L36C50) this should only happen when no resource is provided: > The SDK MUST provide access...
**Description** It is currently confusing which packages implement auto-configure and to which extent. We've previously auto-instantiated propagators from `sdk-trace-base` and `sdk-trace-node`. In SDK 2.0 we should move any auto-configuration functionality...
Currently, we don't auto-configure a `LogRecordProcessor`/exporter combination when using the `@opentelemetry/sdk-node` package. Goal of this issue is to implement exporter selection for metrics based on this specification: - https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#exporter-selection **For...