Ddtrace

Latest version: v2.17.3

Safety actively analyzes 688792 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 39 of 44

0.11.1

Not secure
**Improvements**

* [bottle] use the `route` argument in `TracePlugin`, to support Bottle 0.11.x (439)

**Bugfixes**

* [django] gunicorn gevent worker wasn't instrumenting database connections (442)
* [django] remove `MIDDLEWARE_CLASSES` deprecation warning from tests (444)
* [django] ensure only `MIDDLEWARE` or `MIDDLEWARE_CLASSES` are loaded with tracing middlewares (446)

Read the [full changeset](https://github.com/DataDog/dd-trace-py/compare/v0.11.0...v0.11.1) and the [release milestone](https://github.com/DataDog/dd-trace-py/milestone/18?closed=1).
---

0.11.0

Not secure
**Security fixes**

* [dbapi] remove `sql.query` tag from SQL spans, so that the content is properly obfuscated in the Agent. This security fix is required to prevent wrong data collection of reported SQL queries. This issue impacts only MySQL integrations and NOT `psycopg2` or `sqlalchemy` while using the PostgreSQL driver. (421)

**New integrations**

* [django] add support for Django 2.0 (415 -- thanks sciyoshi!)
* [mysql] `MySQL-python` and `mysqlclient` packages are currently supported (376 -- thanks yoichi!)
* [psycopg2] add support for version 2.4 (424)
* [pylons] Pylons >= 0.9.6 is officially supported (416)

**Bugfixes**

* [core] `ddtrace-run` script accepts `DATADOG_PRIORITY_SAMPLING` to enable [Priority Sampling](http://pypi.datadoghq.com/trace/docs/#priority-sampling) (426)
* [pylons] add distributed tracing via kwarg and environment variable (425, [docs](http://pypi.datadoghq.com/trace/docs/#module-ddtrace.contrib.pylons))
* [pylons] `ddtrace-run` script can patch a `PylonsApp` (416)
* [pylons] add tracing to Pylons `render` function (420)

Read the [full changeset](https://github.com/DataDog/dd-trace-py/compare/v0.10.1...v0.11.0) and [0.11.0 milestone](https://github.com/DataDog/dd-trace-py/milestone/15?closed=1).
---

0.10.1

Not secure
**Distributed Tracing**
Add distributed tracing using integration settings for the following libraries/frameworks:
* `bottle` (382)
* `requests` (372)
* `pyramid` (403)

**Improvements**
* [core] provide constants to pick Priority Sampling values (391)
* [django] add support for Django Rest Framework (389)
* [tooling] add missing classifiers for pypi (395 -- thanks PCManticore)
* [tornado] patch `concurrent.futures` if available, improving the way traces are built when propagation happens between threads (362 -- thanks codywilbourn)

**Bugfixes**
* [httplib] don't overwrite return value (380 -- thanks yoichi)
* [psycopg2] patch all imports of `register_type` (393 -- thanks stj)
* [pyramid] keep request as part of `render` kwargs (384 -- thanks joual)
* [pyramid] use pyramid `HTTPExceptions` as valid response types (401, 386 -- thanks TylerLubeck)
* [requests] add `unpatch` and double-patch protection (404)
* [flask] don't override code of already handled errors (390, 409)
* [flask] allow mutability of `resource` field within request (353, 410)

Read the [full changeset](https://github.com/DataDog/dd-trace-py/compare/v0.10.0...v0.10.1).
---

0.10.0

Not secure
**Distributed Sampling (beta)**

New feature that propagates the sampling priority across services. This is useful to mark traces as "don’t keep the trace" or "must have" when distributed tracing is used. This new functionality requires at least the Datadog Agent 5.19+. Frameworks with out-of-the-box support are: Django, Flask, Tornado (358, 325, 359, 364, 366, 365, 371, [docs](http://pypi.datadoghq.com/trace/docs/#priority-sampling))

**Improvements**
* [core] update the Context propagation API, that includes a new way to retrieve and set the current active `Span` context. (339)
* [core] implement Propagators API to simplify Distributed Tracing. You can use `HTTPPropagator` class to inject and extract the tracing context in HTTP headers (363, 374 [docs](http://pypi.datadoghq.com/trace/docs/#ddtrace.propagation.http.HTTPPropagator))
* [celery] use service name from `DATADOG_SERVICE_NAME` env var, if defined (347 -- thanks miketheman)
* [django] respect env Agent host and port if defined (354 -- thanks spesnova)

**Bugfixes**
* [pylons] handle exception with non standard 'code' attribute (350)
* [pyramid] the application was not traced when the tween list was explicitly specified (349)

Read the full [changeset](https://github.com/DataDog/dd-trace-py/compare/v0.9.2...v0.10.0)
---

0.9.2

Not secure
**New features**
* [django] disable database or cache instrumentation via settings so that each Django component instrumentation can be disabled (314, [docs](http://localhost:8000/#module-ddtrace.contrib.django) -- thanks mcanaves)
* [django] it's not required anymore to add the Django middleware because the Django app ensures that it is installed. You can safely remove `ddtrace.contrib.django.TraceMiddleware` for your middleware list after the upgrade. This is not mandatory but suggested (314, 346)
* [cassandra] trace `execute_async()` operations (333)

**Bugfixes**
* [mysql] prevent the Pin from attaching empty tags (327)
* [django] fixed the initialization order to prevent logs when the tracer is disabled (334)
* [sqlite3] add tests to ensure that services are properly sent (337)
* [pyramid] fixed Pyramid crash when 'include()' is used with relative import paths (342)
* [pylons] re-raise the exception with the original traceback in case of errors. Before Pylons exceptions were correctly handled but hidden by the tracing middleware. (317)
* [pyramid] disable autocommit in Pyramid patching, to avoid altering the `Configurator` behavior (343)
* [flask] fix Flask instrumentation that didn't close Jinja spans if an error was thrown (344)

**Integration coverage**
* officially support ElasticSearch 1.6+ (341)

**Documentation**
* fixed usage examples for `patch_all()` and `patch()` (321 -- thanks gomlgs)
* added a section about updating the hostname and port (335)

Read the [full changeset](https://github.com/DataDog/dd-trace-py/compare/v0.9.1...v0.9.2).
---

0.9.1

Not secure
**New features**
* [core] add a processing pipeline to the `AsyncWorker`, so that traces can be filtered easily. This change doesn't have any performance impact with existing installations, and is expected to work well with async frameworks / libraries (303, [docs](http://pypi.datadoghq.com/trace/docs/#trace-filtering))
* [core] add language and library version metadata to keep track of them in the Datadog Agent. All values are sent via headers (289)

**Bugfixes**
* [aiobotocore] update `async with` context manager so that it returns the wrapper instead of the wrapped object (307)
* [boto, botocore] change the service metadata app for AWS with a more meaningful name (315)

**Documentation**
* improving documentation so that it's more explicit how a framework should be auto-instrumented (305, 308)
* add the list of auto-instrumented modules (306)

Read the [full changeset](https://github.com/DataDog/dd-trace-py/compare/v0.9.0...v0.9.1).
---

Page 39 of 44

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.