1.8.0rc1

Release Notes

Upgrade Notes

• ASM: libddwaf upgraded to version 1.6.1 using a new library loading mechanism
• profiling: upgrades the profiler to support the v2.4 backend API for profile uploads, using a new request format.

Deprecation Notes

• DD_REMOTECONFIG_POLL_SECONDS environment variable is deprecated and will be removed in v2.0. Please use DD_REMOTE_CONFIG_POLL_INTERVAL_SECONDS instead.

New Features

• CI Visibility: Add support for CI provider buddy.works
• The component tag has been added for all auto-instrumented spans. The value of the component tag is equal to the name of the integration that produced the span.
• tracing: Adds support for IPv6 agent hostnames for DD_AGENT_HOST.
• elasticsearch: Update elasticsearch integration to add support for opensearch-py. See the elasticsearch documentation for more information.
• ASM: New Application Security Events Tracking API, starting with the functions track_user_login_success_event and
  track_user_login_failure_event for tracking user logins (it will also internally call set_user) and track_custom_event for any custom events. You can find these functions in the ddtrace.appsec.trace_utils module. Calling these functions will create new tags under the appsec.events namespace (appsec.events.user.login for logins) allowing you to track these events with Datadog. In the future this will be used to provide protection against account takeover attacks (ATO). Public documentation will be online soon.
• tornado: Support custom error codes: https://ddtrace.readthedocs.io/en/stable/advanced_usage.html#custom-error-codes.
• CI Visibility: Support reliably linking tests to the pipeline that executed them.

Known Issues

• profiling: There is currently a known Python 3.11 compatibility issue where the stack collector does not properly access PyFrameObject member values, as PyFrameObject is now created and computed lazily in Python 3.11. Until this is fixed, we advise against enabling the profiler while using Python 3.11.
• profiling: There is currently a known performance regression issue with the profiler's code provenance feature. Note that this feature is disabled by default and will only be enabled if DD_PROFILING_ENABLE_CODE_PROVENANCE is set to true.

Bug Fixes

• This fix improves a cryptic error message encountered during some pip install ddtrace runs under pip versions <18.
• profiling: This fix resolves an issue in Python 3.11 where a PyFrameObject strong reference count was not properly decremented in the stack collector.

Other Changes

• profiler: CPU overhead reduction.

1.7.3

Bug Fixes

• profiling: This fix resolves an issue in Python 3.11 where a PyFrameObject strong reference count was not properly decremented in the stack collector.

1.7.2

Bug Fixes

• Fix for ValueError when @ is not present in network location but other part of the url.

1.6.6

Bug Fixes

• Fix for ValueError when @ is not present in network location but other part of the url.

0.61.5

Bug Fixes

• Fix for ValueError when @ is not present in network location but other part of the url.

1.7.1

Bug Fixes

• This fix removes unintended url parts in the http.url tag.

1.6.5

Bug Fixes

• This fix removes unintended url parts in the http.url tag.

0.61.4

Bug Fixes

• This fix removes unintended url parts in the http.url tag.

1.7.0

Upgrade Notes

• The default propagation style configuration changes to DD_TRACE_PROPAGATION_STYLE=tracecontext,datadog. To only support Datadog propagation and retain the existing default behavior, set DD_TRACE_PROPAGATION_STYLE=datadog.
• tracer: support for Datadog Agent v5 has been dropped. Datadog Agent v5 is no longer supported since ddtrace==1.0.0. See https://ddtrace.readthedocs.io/en/v1.0.0/versioning.html#release-support for the version support.
• The configured styles in DD_TRACE_PROPAGATION_STYLE_EXTRACT are now evaluated in order to specification. To keep the previous fixed evaluation order, set: DD_TRACE_PROPAGATION_STYLE_EXTRACT=datadog,b3,b3 single header.
• tracing: upgrades the default trace API version to v0.5 for non-Windows systems. The v0.5 trace API version generates smaller payloads, thus increasing the throughput to the Datadog agent especially with larger traces.
• tracing: configuring the v0.5 trace API version on Windows machines will raise a RuntimeError due to known compatibility issues. Please see #4829 for more details.

Deprecation Notes

• propagation: Configuration of propagation style with DD_TRACE_PROPAGATION_STYLE=b3 is deprecated and will be removed in version 2.0.0. Please use the newly added DD_TRACE_PROPAGATION_STYLE=b3multi instead.
• aws: The boto, botocore and aiobotocore integrations no longer include all API parameters by default. To retain the deprecated behavior, set the environment variable DD_AWS_TAG_ALL_PARAMS=1. The deprecated behavior and environment variable will be removed in v2.0.0.

New Features

• django: add configuration option to allow a resource format like {method}{handler}.{url_name} in projects with Django <2.2.0
• django: Adds the DD_DJANGO_INCLUDE_USER_NAME option to toggle whether the integration sets the django.user.name tag.
• Added environment variable DD_TRACE_PROPAGATION_STYLE to configure both injection and extraction propagation styles. The configured styles can be overridden with environment variables DD_TRACE_PROPAGATION_STYLE_INJECT and DD_TRACE_PROPAGATION_STYLE_EXTRACT.
• tracing: This introduces none as a supported propagator for trace context extraction and injection. When none is the only propagator listed, the corresponding trace context operation is disabled. If there are other propagators in the inject or extract list, the none propagator has no effect. For example DD_TRACE_PROPAGATION_STYLE=none
• tracing: Adds support for W3C Trace Context propagation style for distributed tracing. The traceparent and tracestate HTTP headers are enabled by default for all incoming and outgoing HTTP request headers. The Datadog propagation style continue to be enabled by default.
• flask: Adds support for streamed responses. Note that two additional spans: flask.application and flask.response will be generated.
• profiling: Adds support for Python 3.11.
• celery: Enhances context tags containing dictionaries so that their contents are sent as individual tags (issue #4771).
• ASM: One click activation enabled by default using Remote Configuration Management (RCM). Set DD_REMOTE_CONFIGURATION_ENABLED=false to disable this feature.

Bug Fixes

• ASGI: response headers are correctly processed instead of ignored
• ASM: Do not raise exceptions when failing to parse XML request body.
• ASM: fix a body read problem on some corner case where don't passing the content length makes wsgi.input.read() blocks.
• aws: We are reducing the number of API parameters that the boto, botocore and aiobotocore integrations collect as span tags by default. This change limits span tags to a narrow set of parameters for specific AWS APIs using standard tag names. To opt out of the new default behavior and collect no API parameters, set the environment variable DD_AWS_TAG_NO_PARAMS=1. To retain the deprecated behavior and collect all API parameters, set the environment variable DD_AWS_TAG_ALL_PARAMS=1.
• Remove forbiddenfruit as dependency and rollback wrapt changes where forbiddenfruit was called. IAST: Patch builtins only when IAST is enabled.
• httpx: Fixes an incompatibility from httpx==0.23.1 when the URL.raw property is not available.
• Fix error in patching functions. forbiddenfruit package has conflicts with some libraries such as asynctest. This conflict raises AttributeError exception. See issue #4484.
• tracer: This fix resolves an issue where the rate limiter used for span and trace sampling rules did not reset the time since last call properly if the rate limiter already had max tokens. This fix resets the time since last call always, which leads to more accurate rate limiting.
• Ensure that worker threads that run on start-up are recreated at the right time after fork on Python < 3.7.
• tracing: This fix resolves an issue where the DD_SERVICE_MAPPING mapped service names were not used when updating span metadata with the DD_VERSION set version string.
• wsgi: This fix resolves an issue where BaseException raised in a WSGI application caused spans to not be submitted.
• library injection: Pin the library version in the library injection image. Prior, the latest version of ddtrace would always be installed, regardless of the image version.
• Fix error in the agent response payload when the user disabled ASM in a dashboard using 1-click Remote Configuration.
• The specification of DD_TRACE_PROPAGATION_STYLE_EXTRACT now respects the configured styles evaluation order. The evaluation order had previously been fixed and so the configured order was ignored.
• tracing: Ensures that encoding errors due to wrong span tag types will be logged. Previously, if non-text span tags were set, this resulted in v0.5 encoding errors to be output to stderr instead of to a logger.
• dynamic instrumentation: Remove unnecessary log line from application start up
• botocore: Before this change, the botocore integration stripped newlines from the JSON string encoded in the data blob of Amazon Kinesis records. This change includes a terminating newline if it is present in the decoded data.
• telemetry: This fix resolves an issue when we try to fetch platform.libc_ver() on an unsupported system.

Known Issues

• profiling: There is currently a known performance regression issue with the profiler's code provenance feature. Note that this feature is disabled by default and will only be enabled if DD_PROFILING_ENABLE_CODE_PROVENANCE is set to true.

Other Changes

• Kubernetes library injection: run commands as non-root user.
• tracing: The value of ddtrace.constants.PID has been changed from system.pid to process_id. All spans will now use the metric tag of process_id instead.
• tracing: The exception logged for writing errors no longer includes a long, unhelpful stack trace. The message now also includes the number of traces dropped and the number of retries attempted.

1.7.0rc4

Known Issues

• profiling: There is currently a known performance regression issue with the profiler's code provenance feature. Note that this feature is disabled by default and will only be enabled if DD_PROFILING_ENABLE_CODE_PROVENANCE is set to true.