Marc Pichler
Marc Pichler
### Affected Repository https://github.com/open-telemetry/opentelemetry-js-contrib ### Requested changes - Give write permissions to @opentelemetrybot - Create a fine-grained PAT for @opentelemetrybot to create PRs and Releases on the https://github.com/open-telemetry/opentelemetry-js-contrib repository -...
# Feature Request **Is your feature request related to a problem? Please describe.** Currently the `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE` enviornment variable is not used to configure the export temporality ([see here](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/2534ce3a3754648b9f4a10707be19f41393e2221/src/OpenTelemetry.AutoInstrumentation/Configuration/EnvironmentConfigurationMetricHelper.cs#L96)). The spec...
## Which problem is this PR solving? See #4390, the dependency update is blocked as `import-in-the-middle` is updated to a version that's affected by https://github.com/DataDog/import-in-the-middle/issues/57 ## Short description of the...
## Which problem is this PR solving? - replaces `cpx` with `cpx2` where it's used, removes `cpx` where it's not used anymore. Supersedes #4506
**Goal:** We should prototype the attributes instrument advisory parameter as described in the spec. We should ensure that this parameter is appropriately marked as experimental in both the API and...
## API 1.8.0 ### :rocket: (Enhancement) * feat(api): add SugaredTracer for functions not defined in the spec [#3317](https://github.com/open-telemetry/opentelemetry-js/pull/3317) @secustor ### :bug: (Bug Fix) * fix(api): fix unreachable @opentelemetry/api/experimental entry [#4446](https://github.com/open-telemetry/opentelemetry-js/pull/4446)...
## Which problem is this PR solving? We've had problems in the past with the gRPC exporters, as they do not lazy-require the `@grpc/grpc-js` library. This causes problems with `@opentelemetry/instrumentation-grpc`...
Updates next with the latest changes from main. All changes here are pre-reviewed already.
### Is your feature request related to a problem? Please describe. Currently, transport, configuration (options and environment variables) as well as serialization code are all mixed together in the OTLP...
`Span.addLink()` as defined in the [specifcation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#add-link) is currently not implemented. We should implement `Span.addLink()` in both the SDK and API. **Additional Information:** - there are efforts to stabilize `Span.addLink()` (https://github.com/open-telemetry/opentelemetry-specification/issues/3865)...