search

signalfx / splunk-otel-lambda

Splunk distribution of OpenTelemetry Lambda
Apache License 2.0
5 stars 4 forks source link

Bump @splunk/otel from 2.11.0 to 2.12.0 in /nodejs #290

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps @splunk/otel from 2.11.0 to 2.12.0.

Release notes

Sourced from @​splunk/otel's releases.

v2.12.0

Open Telemetry API Core Instrumentations
1.8.0 1.26.0 0.53.0

Changes

  • Add resourceFactory option for traces. Allows for customization of the detected resource. Previously a resource could be provided via tracerConfig, but this overwrote the detected attributes. For backwards compatibility the latter option is still possible. #938
  • Support none value for OTEL_TRACES_EXPORTER and OTEL_METRICS_EXPORTER environment variables. #939
  • Use the default OTEL_BSP_SCHEDULE_DELAY of 5000 instead of 500. This was a workaround for an old BatchSpanProcessor bug where it failed to flush spans fully. #940
  • Disable log sending for Winston instrumentation by default. Add winston-transport package as a dependency in case log collection is enabled. #941
  • Use a synchronous container detector from upstream. #944
  • Add deprecation annotations to signal-specific start calls. #885
  • Upgrade to OpenTelemetry 1.26.0 / 0.53.0. #945
Changelog

Sourced from @​splunk/otel's changelog.

2.12.0

  • Add resourceFactory option for traces. Allows for customization of the detected resource. Previously a resource could be provided via tracerConfig, but this overwrote the detected attributes. For backwards compatibility the latter option is still possible. #938
  • Support none value for OTEL_TRACES_EXPORTER and OTEL_METRICS_EXPORTER environment variables. #939
  • Use the default OTEL_BSP_SCHEDULE_DELAY of 5000 instead of 500. This was a workaround for an old BatchSpanProcessor bug where it failed to flush spans fully. #940
  • Disable log sending for Winston instrumentation by default. Add winston-transport package as a dependency in case log collection is enabled. #941
  • Use a synchronous container detector from upstream. #944
  • Add deprecation annotations to signal-specific start calls. #885
  • Upgrade to OpenTelemetry 1.26.0 / 0.53.0. #945
Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)