build(deps): bump ddtrace from 1.9.3 to 2.0.2

[dependabot]

Bumps ddtrace from 1.9.3 to 2.0.2.

Release notes

Sourced from ddtrace's releases.

2.0.2

Bug Fixes

• DSM: fix off-by-one metric issue and error where statistics weren't calculated when the core API was used.
• tracing: Fix an issue with some integrations, such as OpenAI, that caused an exception on start-up when using gevent.
• IAST: fix executed sink telemetry metric as it is not really linked to vulnerability report.
• This fix eliminates some reference leaks and C-API usage in the _iast module.
• tracing: Increases the maximum payload size and buffer size from 8MB to 20MB. Also decreases the maximum number of spans in trace chunks when DD_TRACE_PARTIAL_FLUSH_ENABLED=True. This ensures large traces are correctly encoded and submitted. This should decrease the occurrence of "failed to send traces" error logs.

Other Changes

• remote config: change log levels of messages about agent down or request config to debug level.

2.0.1

Bug Fixes

• This fix resolves an issue where the library failed to install due to dependency conflicts caused by restrictive version specifiers on the psutil and Wrapt libraries.
• openai: This fix resolves an issue where chat completion requests with function calls led to failing to tag null message content fields in the chat completion response.
• profiling: Load the protobuf module only if needed to avoid interfering with the module state for applications that also make use of it. The protobuf module is used in file and classic Python HTTP export. It is not needed for the libdatadog-based exporter.
• lib-injection: changes the log output to opt-in. Logging to stderr could interfere with applications. Logs can still be sent to stderr using DD_TRACE_DEBUG=1.

2.0.0

Prelude

The Datadog APM Python team is happy to announce the release of v2.0.0 of ddtrace. This release drops support for Python 2.7, 3.5, and 3.6. This release adds support for Python 3.12.

[!IMPORTANT] If you are on version of Python not supported by v2, we will continue to maintain the ddtrace v1 with bug fixes.

[!NOTE] Before upgrading to v2.0.0, we recommend users install ddtrace~=1.18.0 and enable deprecation warnings. All removals to the library interface and environment variables in v2 were deprecated in the 1.x release line.

[!NOTE] The changes to environment variables apply only to the configuration of the ddtrace library and not the Datadog Agent.

Upgrading summary

Functionality changes

The default logging configuration functionality of ddtrace has been changed to avoid conflicting with application logging configurations. DD_CALL_BASIC_CONFIG has been removed and the ddtrace logger will log to stdout by default, or a log file as specified using DD_TRACE_LOG_FILE.

Setting the environment variable DD_TRACE_PROPAGATION_STYLE='b3' to enable B3 propagation has been removed. Please use DD_TRACE_PROPAGATION_STYLE='b3multi' instead.

Removed deprecated environment variables

These environment variables have been removed. In all cases the same functionality is provided by other environment variables and replacements are provided as recommended actions for upgrading.

... (truncated)

Commits

• 466106a fix(iast): decouple executed sink metric call [backport 2.0] (#7177)
• 34462ac fix: reference leaks and incorrect C-API usage in _stacktrace.c [backport 2.0...
• 7c1b921 chore(kafka): use core api for data streams monitoring [backport 2.0] (#7163)
• ad31d75 fix(internal): no lazy bytecode imports [backport 2.0] (#7170)
• c242dfb fix(tracing): resolves issues encoding and sending large trace payloads [back...
• f5f02d0 chore(tests): tracer test relaxed [backport 2.0] (#7172)
• 919628d chore(asm): rc logs to debug level [backport 2.0] (#7088)
• 14b7349 fix: revert restriction on psutil and wrapt versions [backport 2.0] (#7168)
• 6557768 fix(lib-injection): log only to stderr when in debug mode [backport 2.0] (#7167)
• b959b59 chore(ci): fix scheduled system tests (backport #7105 to 2.0) (#7111)
• 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 #198.