Ddtrace

Bug Fixes

- Pin `protobuf` version to `<3.18` for Python \<=3.5 due to support being dropped.

---

Bug Fixes

- Pin `setup_requires` dependency `setuptools_scm[toml]>=4,<6.1` to avoid breaking changes.

---

Deprecation Notes

- Removed the `collect_metrics` argument from `Tracer.configure`. See the release notes for v0.49.0 for the migration instructions.

New Features

- Add tracing support for the `httpx` library. Supported versions `>=0.14.0`.

- ASGI: store the ASGI span in the scope. The span can be retrieved with the
`ddtrace.contrib.asgi.span_from_scope` function.

- Submit runtime metrics as distribution metrics instead of gauge metrics.

- Support flask-caching (\>= 1.10.0) with the Flask-Cache tracer.

- Only for CI Visibility (<span class="title-ref">pytest</span> integration): It is now possible to specify any of the following git metadata through environment variables:
- \`DD_GIT_REPOSITORY_URL\`: The url of the repository where the code is stored
- \`DD_GIT_TAG\`: The tag of the commit, if it has one
- \`DD_GIT_BRANCH\`: The branch where this commit belongs to
- \`DD_GIT_COMMIT_SHA\`: The commit hash of the current code
- \`DD_GIT_COMMIT_MESSAGE\`: Commit message
- \`DD_GIT_COMMIT_AUTHOR_NAME\`: Commit author name
- \`DD_GIT_COMMIT_AUTHOR_EMAIL\`: Commit author email
- \`DD_GIT_COMMIT_AUTHOR_DATE\`: The commit author date (ISO 8601)
- \`DD_GIT_COMMIT_COMMITTER_NAME\`: Commit committer name
- \`DD_GIT_COMMIT_COMMITTER_EMAIL\`: Commit committer email
- \`DD_GIT_COMMIT_COMMITTER_DATE\`: The commit committer date (ISO 8601)

Bug Fixes

- ASGI: handle decoding errors when extracting headers for trace propagation.

- Corrected some typing annotations for PEP 484 compliance

- Django: add support for version 3.1+ ASGI applications. A different codepath is taken for requests starting in Django 3.1 which led to the top level span not being generated for requests. The fix introduces automatic installation of the ASGI middleware to trace Django requests.

- dogpile.cache: handle both kwargs and args in the wrapper functions (using
only kwargs would result in an IndexError.

- Fixes an issue with the Django integration where if the `urlconf` changes at any point during the handling of the request then the resource name will only be `<METHOD> 404`. This fix moves resource name resolution to the end of the request.

- Fixes error with tagging non-string Flask view args.

- `werkzeug.exceptions.NotFound` 404 errors are no longer raised and logged as a server error in the Flask integration.

- Fixes type hinting for `**patch_modules` parameter for `patch`/`patch_all` functions.

- Fixes an issue when using the pytest plugin with doctest which raises an `AttributeError` on `DoctestItem`.

- Fixes a bug in the pytest plugin where xfail test cases in a test file with a module-wide skip raises attribute errors and are marked as xfail rather than skipped.

- Fixed the handling of sanic endpoint paths with non-string arguments.

- opentracer: don't override default tracing config for the <span class="title-ref">ENABLED</span>,
<span class="title-ref">AGENT_HOSTNAME</span>, <span class="title-ref">AGENT_HTTPS</span> or <span class="title-ref">AGENT_PORT</span> settings.

---

Bug Fixes

- Pin `setup_requires` dependency `setuptools_scm[toml]>=4,<6.1` to avoid breaking changes.

---

New Features

- ASGI: store the ASGI span in the scope. The span can be retrieved with the
`ddtrace.contrib.asgi.span_from_scope` function.

Bug Fixes

- ASGI: handle decoding errors when extracting headers for trace propagation.
- Corrected some typing annotations for PEP 484 compliance
- Django: add support for version 3.1+ ASGI applications. A different codepath is taken for requests starting in Django 3.1 which led to the top level span not being generated for requests. The fix introduces automatic installation of the ASGI middleware to trace Django requests.
- Fixes error with tagging non-string Flask view args.
- Fixes type hinting for `**patch_modules` parameter for `patch`/`patch_all` functions.
- Fixes a bug in the pytest plugin where xfail test cases in a test file with a module-wide skip raises attribute errors and are marked as xfail rather than skipped.

---

Upgrade Notes

- The legacy Django configuration method (deprecated in 0.34) has been removed.
- botocore: Update trace propagation format for directly invoked Lambda functions. This breaks compatibility with Lambda functions instrumented with datadog-lambda-python \< v41 or datadog-lambda-js \< v3.57.0. Please upgrade datadog-lambda-\* in invoked lambda functions, or engage legacy compatibility mode in one of two ways:
- ddtrace.config.botocore.invoke_with_legacy_context = True
- DD_BOTOCORE_INVOKE_WITH_LEGACY_CONTEXT=true

Deprecation Notes

- `monkey.patch_module` is deprecated.
- `monkey.get_patch_module` is deprecated.

New Features

- Added support for `jinja2~=3.0.0`.
- The pytest integration now uses the name of the repository being tested as the default test service name.
- Added support for `aiopg~=0.16.0`.
- Add MariaDB integration.
- The profiler now exports active tasks for CPU and wall time profiles.

Bug Fixes

- Fixes an issue with enabling the runtime worker introduced in v0.49.0 where no runtime metrics were sent to the agent.
- Fix pymongo 3.12.0+ spans not being generated.
- Fixed JSON encoding errors in the pytest plugin for parameterized tests with dictionary parameters with tuple keys. The pytest plugin now always JSON encodes the string representations of test parameters.
- Fixed JSON encoding errors in the pytest plugin for parameterized tests with complex Python object parameters. The pytest plugin now defaults to encoding the string representations of non-JSON serializable test parameters.
- Fix a possible NoneType error in the WSGI middleware start_response method.

---