Bump ddtrace from 1.15.0 to 1.17.0

[dependabot]

Bumps ddtrace from 1.15.0 to 1.17.0.

Release notes

Sourced from ddtrace's releases.

1.17.0

For W3C Trace Context, this release adds tracecontext to the default trace propagation extraction and injection styles. The new defaults are:

• Extraction: Datadog,b3multi,b3,tracecontext
• Injection: Datadog,tracecontext

And to increase interoperability with tracecontext, 128-bit Trace ID generation is now the default.

For OpenTelemetry, this release adds support for converting OpenTelemetry Trace Semantic Conventions into equivalent Datadog trace semantics. Also, it's now possible to configure top-level Datadog span fields using OpenTelemetry span attributes (DataDog/dd-trace-rb#3262).

For CI Visibility, you can now manually create CI traces and spans with the newly released API.

Added

• OpenTelemetry: Parse OpenTelemetry semantic conventions to Datadog's (#3273)
• OpenTelemetry: Support span reserved attribute overrides (#3262)
• Tracing: Ensure W3C tracestate is always propagated (#3255)

Changed

• Tracing: Set 128-bit trace_id to true by default (#3266)
• Tracing: Default trace propagation styles to Datadog,b3multi,b3,tracecontext (#3248,#3267)
• Ci-App: Upgraded datadog-ci dependency to 0.4 (#3270)

Read the full changeset and the release milestone.

1.16.2

This release reverts a change to appsec response body parsing that was introduced in 1.16.0 that may cause memory leaks.

Fixed

• Appsec: Revert parse response body fix introduced in 1.16.0 (#3252)

Read the full changeset and the release milestone.

1.16.1

Fixed

• Tracing: Fix concurrent-ruby future propagation without active_trace (#3242)
• Tracing: Fix host injection error handling (#3240)

Read the full changeset and the release milestone.

1.16.0

This release includes a security change for the Tracing Redis integration:

Currently, the Datadog Agent removes command arguments from the resource name. However there are cases, like Redis compressed keys, where this obfuscation cannot correctly remove command arguments. To safeguard that situation, the resource name set by the tracer will only be the command (e.g. SET) with no arguments. To retain the previous behavior and keep arguments in the span resource, with the potential risk of some command arguments not being fully obfuscated, set DD_REDIS_COMMAND_ARGS=true or set the option c.instrument :redis, command_args: true.

Added

... (truncated)

Changelog

Sourced from ddtrace's changelog.

[1.17.0] - 2023-11-22

For W3C Trace Context, this release adds tracecontext to the default trace propagation extraction and injection styles. The new defaults are:

• Extraction: Datadog,b3multi,b3,tracecontext
• Injection: Datadog,tracecontext

And to increase interoperability with tracecontext, 128-bit Trace ID generation is now the default.

For OpenTelemetry, this release adds support for converting OpenTelemetry Trace Semantic Conventions into equivalent Datadog trace semantics. Also, it's now possible to configure top-level Datadog span fields using OpenTelemetry span attributes (DataDog/dd-trace-rb#3262).

For CI Visibility, you can now manually create CI traces and spans with the newly released API.

Added

• OpenTelemetry: Parse OpenTelemetry semantic conventions to Datadog's (#3273[])
• OpenTelemetry: Support span reserved attribute overrides (#3262[])
• Tracing: Ensure W3C tracestate is always propagated (#3255[])

Changed

• Tracing: Set 128-bit trace_id to true by default (#3266[])
• Tracing: Default trace propagation styles to Datadog,b3multi,b3,tracecontext (#3248[],#3267)
• Ci-App: Upgraded datadog-ci dependency to 0.4 (#3270[])

[1.16.2] - 2023-11-10

This release reverts a change to appsec response body parsing that was introduced in 1.16.0 that may cause memory leaks.

Fixed

• Appsec: Revert parse response body fix introduced in 1.16.0 (#3252[])

[1.16.1] - 2023-11-08

Fixed

• Tracing: Fix concurrent-ruby future propagation without active_trace (#3242[])
• Tracing: Fix host injection error handling (#3240[])

[1.16.0] - 2023-11-03

This release includes a security change for the Tracing Redis integration:

Currently, the Datadog Agent removes command arguments from the resource name. However there are cases, like Redis compressed keys, where this obfuscation cannot correctly remove command arguments. To safeguard that situation, the resource name set by the tracer will only be the command (e.g. SET) with no arguments. To retain the previous behavior and keep arguments in the span resource, with the potential risk of some command arguments not being fully obfuscated, set DD_REDIS_COMMAND_ARGS=true or set the option c.instrument :redis, command_args: true.

Added

• Tracing: Propagate trace through Concurrent::Promises.future (#1522[])
• Core: Name Datadog::Core::Remote::Worker thread (#3207[])

Changed

... (truncated)

Commits

• b4c9019 Merge pull request #3275 from DataDog/bump_to_version_1.17.0
• 9b506b8 Update lockfiles for ddtrace 1.17.0
• 07cd631 Bump version 1.16.2 to 1.17.0
• cba6891 Add 1.17.0 to CHANGELOG.md
• a58330f Merge pull request #3273 from DataDog/swap-op-with-resource
• 93df84f Restore master gemfile
• 2c06b2d merge
• b54cbbb Convert OTel semantic convention to Datadog's
• 3becb40 set 128-bit trace_id to true by default (#3266)
• f7c741d Merge pull request #3272 from DataDog/revert-3260-package-arm
• Additional commits viewable in compare view

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 <dependency name> 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)

[dependabot]

Superseded by #41.