ddtrace 3.10.0rc2

on Python PyPI

Deprecation Notes

• Tracing
  • The escaped and timestamp arguments in the record_exception method are deprecated and will be removed in version 4.0.0.

New Features

• LLMObs:

  • google_genai: Introduces tracing support for Google's Generative AI SDK for Python's generate_content and generate_content_stream methods.
    See the docs for more information.

• Tracing:

  • azure_servicebus: Add support for Azure Service Bus producers.
  • azure_functions: Add distributed tracing support for Service Bus triggers.
  • ddtrace-api: Adds patching of ddtrace_api.tracer.set_tags to the ddtrace_api integration

Bug Fixes

• CI Visibility:

  • This fix resolves an issue where code coverage would not be enabled if ddtrace was enabled via the PYTEST_ADDOPTS environment variable.

• Dynamic Instrumentation:

  • Fixed an issue with the instrumentation of the first line of an iteration block (e.g. for loops) that could have caused undefined behavior.
  • Fixed an issue that prevented line probes from being instrumented on a line containing just the code try: for CPython 3.11 and later.

• Tracing:

  • This fix resolves an issue where the @tracer.wrap() decorator failed to preserve return values from generator functions, causing StopIteration.value to be None instead of the actual returned value.
  • rq: Enable parsing distributed tracing metadata in perform job

• LLMObs:

  • langchain: Resolved an AttributeError that could occur when async tasks are cancelled during agenerate calls.

• Logging:

  • Ensured that ddtrace.tracer.get_log_correlation_context() returns the expected log correlation attributes (e.g., dd.trace_id, dd.span_id, dd.service instead of trace_id, span_id, service). This change aligns the method's output with the attributes in ddtrace log-correlation docs.
  • Fixed an issue where ddtrace.tracer.get_log_correlation_context() would return the service name of the current span instead of the global service name.

Other Changes

• Library Injection:
  • Additional fields have been added to the telemetry forwarder used during Single Step to surface troubleshooting insights in the Datadog UI.