Releases: DataDog/dd-trace-py
1.1.0
New Features
-
Fixes deprecation warning for
asyncio.coroutinedecorator. -
psycopg2: add option to enable tracing
psycopg2.connectmethod.See our
psycopg2documentation for more information. -
Add support to reuse HTTP connections when sending trace payloads to the agent. This feature is disabled by default. Set
DD_TRACE_WRITER_REUSE_CONNECTIONS=trueto enable this feature. -
MySQLdb: Added optional tracing for MySQLdb.connect, using the configuration option here.
-
The profiler now supports profiling
asyncio.Lockobjects. -
Add support for injecting and extracting B3 propagation headers.
See DD_TRACE_PROPAGATION_STYLE_EXTRACT and DD_TRACE_PROPAGATION_STYLE_INJECT configuration documentation to enable.
Bug Fixes
-
botocore: omit
SecretBinaryandSecretStringfrom span metadata for calls to Secrets Manager. -
Fix issue building
ddtracefor the Pyston Python implementation by not building the_memallocextension anymore when using Pyston. -
tracer.get_log_correlation_context(): use active context in addition to active span. Formerly just the span was used and this would break cross execution log correlation as a context object is used for the propagation. -
opentracer: update
set_tagandset_operation_nameto return a reference to the span to match the OpenTracing spec. -
The CPU profiler now reports the main thread CPU usage even when asyncio tasks are running.
1.1.0rc3
Bug Fixes
- Fixes deprecation warning for
asyncio.coroutinedecorator.
1.0.2
Bug Fixes
- Fixes deprecation warning for
asyncio.coroutinedecorator.
0.60.5
Bug Fixes
- Fixes deprecation warning for
asyncio.coroutinedecorator.
1.1.0rc2
1.1.0rc1
New Features
-
fastapi: add support for tracing
fastapi.routing.serialize_response.This will give an insight into how much time is spent calling
jsonable_encoderwithin a given request. This does not provide visibility into how long it takes forResponse.render/json.dumps. -
Add support to reuse HTTP connections when sending trace payloads to the agent. This feature is disabled by default. Set
DD_TRACE_WRITER_REUSE_CONNECTIONS=trueto enable this feature. -
MySQLdb: Added optional tracing for MySQLdb.connect, using the configuration option here.
-
The profiler now supports profiling
asyncio.Lockobjects. -
Add support for injecting and extracting B3 propagation headers.
See DD_TRACE_PROPAGATION_STYLE_EXTRACT and DD_TRACE_PROPAGATION_STYLE_INJECT configuration documentation to enable.
Bug Fixes
-
botocore: omit
SecretBinaryandSecretStringfrom span metadata for calls to Secrets Manager. -
Fix issue building
ddtracefor the Pyston Python implementation by not building the_memallocextension anymore when using Pyston. -
tracer.get_log_correlation_context(): use active context in addition to
active span. Formerly just the span was used and this would break cross execution log correlation as a context object is used for the propagation. -
opentracer: update
set_tagandset_operation_nameto return a
reference to the span to match the OpenTracing spec. -
The CPU profiler now reports the main thread CPU usage even when asyncio tasks are running.
0.60.4
Other Notes
- internal: mark trace payloads as being partial flushed
- internal: improve debug logs for tracer patching
1.0.1
Bug Fixes
-
Fix issue building
ddtracefor the Pyston Python implementation by not building the_memallocextension anymore when using Pyston. -
tracer.get_log_correlation_context(): use active context in addition to active span. Formerly just the span was used and this would break cross execution log correlation as a context object is used for the propagation. -
The CPU profiler now reports the main thread CPU usage even when asyncio tasks are running.
0.60.3
Bug Fixes
- Fix issue building
ddtracefor the Pyston Python implementation by not building the_memallocextension anymore when using Pyston. - The CPU profiler now reports the main thread CPU usage even when asyncio tasks are running.
1.0.0
The Datadog APM Python team is happy to announce the release of v1.0.0 of ddtrace. This release introduces a formal versioning policy that simplifies the public interface and defines a release version policy for backwards compatible and incompatible changes to the public interface.
A full summary and details are included in the v1.0.0 Release Notes.
Important
Before upgrading to v1.0.0, we recommend users install ddtrace>=0.60.0,<1.0.0 and enable deprecation warnings. All removals to the library interface and environment variables were deprecated on 0.x branch. Consult Upgrade 0.x for recommendations on migrating from the 0.x release branch.