Bump ddtrace from 2.13.0 to 2.15.1

[dependabot]

Bumps ddtrace from 2.13.0 to 2.15.1.

Release notes

Sourced from ddtrace's releases.

2.15.1

Bug Fixes

• LLM Observability: This fix resolves two issues with annotation contexts:
  - annotations registered via annotation contexts were being applied globally. Annotations are now only applied to the current trace context and do not pollute to other threads & processes. - annotations from nested annotation contexts were applied in a non-deterministic order. Annotations are now applied in the order they were registered.

• CI Visibility: fixes a bug where CODEOWNERS would incorrectly fail to discard line-level trailing comments (eg: @code/owner # my comment would result in codeowners being parsed as @code/owner, #, my, and comment)

• CI Visibility: fixes unnecessary logging of an exception that would appear when trying to upload git metadata in an environment without functioning git (eg: missing git binary or .git directory)

• dynamic instrumentation: Fixes an issue that prevented dynamic span tags probes from adding the requested tags to the requested span.

• Code Security: This fix resolves an issue where importing the google.cloud.storage.batch module would fail raising an ImportError

• profiling: fix a data race where span information associated with a thread was read and updated concurrently, leading to segfaults

• profiling: resolves an issue where endpoint profiling for stack v2 throws TypeError exception when it is given a Span with None span_type.

Other Changes

• LLM Observability: Updates the merging behavior for tags when LLMObs.annotate is called multiple times on the same span so that the latest value for a tag key overrides the previous value.

2.15.0

New Features

• LLM Observability

  • Introduces prompt and name arguments to LLMObs.annotation_context to support setting an integration generated span's name and prompt field. For more information on annotation contexts, see the docs here.
  • langchain: Adds support for tracing stream calls on LCEL chains, chat completion models, or completion models. Note that due to an upstream issue with the langchain library itself, streamed responses will not be tagged correctly based on the choice index when the underlying model is configured to return n>1 choices. Please refer to this GitHub issue for more details.
  • LangChain streamed calls (llm.stream, chat_model.stream, and chain.stream) submit to LLM Observability.

• CI Visibility

  • Adds the test_session.name tag to test events. The test session name can be set via the DD_TEST_SESSION_NAME environment variable. If DD_TEST_SESSION_NAME is not specified, the test session name is set from the CI job id and the test command.

• Tracing

  • Introduces Code Origin for Span, a new feature that allows collecting information about where entry and exit spans have been created in the user code . This feature is disabled by default and can be enabled by setting the DD_CODE_ORIGIN_FOR_SPANS_ENABLED environment variable to true.
  • botocore: Adds span pointers for successful DynamoDB DeleteItem spans.
  • botocore: Adds span pointers for successful DynamoDB PutItem spans. Table Primary Keys need to be provided with the ddtrace.config.botocore.dynamodb_primary_key_names_for_tables option or the DD_BOTOCORE_DYNAMODB_TABLE_PRIMARY_KEYS environment variable.
  • botocore: Adds span pointers for successful DynamoDB UpdateItem spans.
  • botocore: Adds span pointers for successful S3 CompleteMultipartUpload spans.
  • botocore: Adds span pointers for successful S3 CopyObject spans.
  • Adds DD_TRACE_HTTP_CLIENT_ERROR_STATUSES environment variable to configure the list of HTTP status codes that should be considered errors when instrumenting HTTP servers.

Deprecation Notes

• Tracing
  • The following attributes are now private and should not be accessed directly. The corresponding environment variables should be used instead.
    • Use DD_TRACE_HTTP_CLIENT_TAG_QUERY_STRING instead of ddtrace.config.http_tag_query_string
    • Use DD_TRACE_HEADER_TAGS instead of ddtrace.config.trace_http_header_tags
    • Use DD_TRACE_REPORT_HOSTNAME instead of ddtrace.config.report_hostname

... (truncated)

Changelog

Sourced from ddtrace's changelog.

Changelog

Changelogs for versions not listed here can be found at https://github.com/DataDog/dd-trace-py/releases

---

2.15.0

New Features

• LLM Observability

  • Introduces prompt and name arguments to LLMObs.annotation_context to support setting an integration generated span's name and prompt field. For more information on annotation contexts, see the docs here.
  • langchain: Adds support for tracing stream calls on LCEL chains, chat completion models, or completion models. Note that due to an upstream issue with the langchain library itself, streamed responses will not be tagged correctly based on the choice index when the underlying model is configured to return n>1 choices. Please refer to this GitHub issue for more details.
  • LangChain streamed calls (llm.stream, chat_model.stream, and chain.stream) submit to LLM Observability.

• CI Visibility

  • Adds the test_session.name tag to test events. The test session name can be set via the DD_TEST_SESSION_NAME environment variable. If DD_TEST_SESSION_NAME is not specified, the test session name is set from the CI job id and the test command.

• Tracing

  • Introduces Code Origin for Span, a new feature that allows collecting information about where entry and exit spans have been created in the user code . This feature is disabled by default and can be enabled by setting the DD_CODE_ORIGIN_FOR_SPANS_ENABLED environment variable to true.
  • botocore: Adds span pointers for successful DynamoDB DeleteItem spans.
  • botocore: Adds span pointers for successful DynamoDB PutItem spans. Table Primary Keys need to be provided with the ddtrace.config.botocore.dynamodb_primary_key_names_for_tables option or the DD_BOTOCORE_DYNAMODB_TABLE_PRIMARY_KEYS environment variable.
  • botocore: Adds span pointers for successful DynamoDB UpdateItem spans.
  • botocore: Adds span pointers for successful S3 CompleteMultipartUpload spans.
  • botocore: Adds span pointers for successful S3 CopyObject spans.
  • Adds DD_TRACE_HTTP_CLIENT_ERROR_STATUSES environment variable to configure the list of HTTP status codes that should be considered errors when instrumenting HTTP servers.

Deprecation Notes

• Tracing
  • The following attributes are now private and should not be accessed directly. The corresponding environment variables should be used instead.
    • Use DD_TRACE_HTTP_CLIENT_TAG_QUERY_STRING instead of ddtrace.config.http_tag_query_string
    • Use DD_TRACE_HEADER_TAGS instead of ddtrace.config.trace_http_header_tags
    • Use DD_TRACE_REPORT_HOSTNAME instead of ddtrace.config.report_hostname
    • Use DD_TRACE_HEALTH_METRICS_ENABLED instead of ddtrace.config.health_metrics_enabled
    • Use DD_TRACE_ANALYTICS_ENABLED instead of ddtrace.config.analytics_enabled
    • Use DD_TRACE_CLIENT_IP_HEADER instead of ddtrace.config.client_ip_header
    • Use DD_TRACE_CLIENT_IP_ENABLED instead of ddtrace.config.retrieve_client_ip
    • Use DD_TRACE_PROPAGATION_HTTP_BAGGAGE_ENABLED instead of ddtrace.config.propagation_http_baggage_enabled
    • Set DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP to an empty string instead of setting ddtrace.config.global_query_string_obfuscation_disabled to True (default value is False)
    • Use DD_TRACE_METHODS instead of ddtrace.config.trace_methods
    • Use DD_CIVISIBILITY_LOG_LEVEL instead of ddtrace.config.ci_visibility_log_level
  • Deprecates the DD_TRACE_SAMPLE_RATE environment variable. It will be removed in 3.0.0. Use DD_TRACE_SAMPLING_RULES to configure sampling rates instead.
  • DD_TRACE_API_VERSION=v0.3 is deprecated. Use v0.4 or v0.5 instead.

Bug Fixes

• Code security
  • Resolves an issue where partial matches on function names we aimed to patch were being patched instead of full matches on them.
  • Always report a telemetry log error when an IAST propagation error raises, regardless of whether the _DD_IAST_DEBUG environment variable is enabled or not.
  • Ensures that only the IAST propagation context is cleared instead of all contexts, which could otherwise cause propagation loss in multithreaded applications. Additionally, it improves validations in both the Processor and Vulnerability Reporter, depending on whether IAST is active or not.

... (truncated)

Commits

• 07c4671 fix(iast): add google.auth to the IAST denylist [backport 2.15] (#11243)
• 76ae70b fix(profiling): fix data race when accessing span for thread [backport 2.15] ...
• 8a28a5d chore: format release notes so the release script could parse [backport 2.15...
• b1f1f4d chore(ci): remove django circleci test suite [backport 2.15] (#11223)
• 6d2f7eb fix(di): use enum value for evaluate_at property [backport 2.15] (#11152)
• 530a964 fix(ci_visibility): strip out comments in codeowners [backport 2.15] (#11194)
• a5b6377 fix(ci_visibility): avoid git tracebacks when .git dir is absent [backport 2....
• 242dd30 fix(profiling): handle Spans with None span type for stack v2 endpoint pr...
• 17c5478 fix(llmobs): refactor annotation context implementation [backport 2.15] (#11124)
• c060a72 fix(elasticsearch): set tags on span, regardless of sampling [backport 2.15] ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #233.