Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(llmobs): modify integration patch behavior in llmobs.enable() [backport 2.9] #9434

Merged
merged 2 commits into from
May 29, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 29, 2024

Backport a1a0ea7 from #9398 to 2.9.

This PR changes the LLMObs.enable() argument integrations list of integrations to enable to --> integrations_enabled a boolean flag whether or not the LLM integrations should be patched.

Previously we could use LLMObs.enable(integrations=[...]) to enable which LLMObs integrations to patch, but this is unnecessary functionality that is already supported by ddtrace. Users should just use ddtrace.patch_all()/ddtrace.patch() instead.

Checklist

  • Change(s) are motivated and described in the PR description
  • Testing strategy is described if automated tests are not included in the PR
  • Risks are described (performance impact, potential for breakage, maintainability)
  • Change is maintainable (easy to change, telemetry, documentation)
  • [x ] Library release note guidelines are followed or label changelog/no-changelog is set
  • Documentation is included (in-code, generated user docs, public corp docs)
  • Backport labels are set (if applicable)
  • If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Description motivates each change
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Change is maintainable (easy to change, telemetry, documentation)
  • Release note makes sense to a user of the library
  • Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

…9398)

This PR changes the LLMObs.enable() argument integrations list of
integrations to enable to --> integrations_enabled a boolean flag
whether or not the LLM integrations should be patched.

Previously we could use LLMObs.enable(integrations=[...]) to enable
which LLMObs integrations to patch, but this is unnecessary
functionality that is already supported by ddtrace. Users should just
use ddtrace.patch_all()/ddtrace.patch() instead.

## Checklist

- [x] Change(s) are motivated and described in the PR description
- [x] Testing strategy is described if automated tests are not included
in the PR
- [x] Risks are described (performance impact, potential for breakage,
maintainability)
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x ] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed or label `changelog/no-changelog` is set
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/))
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
- [x] If this PR changes the public interface, I've notified
`@DataDog/apm-tees`.

## Reviewer Checklist

- [x] Title is accurate
- [x] All changes are related to the pull request's stated goal
- [x] Description motivates each change
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- [x] Testing strategy adequately addresses listed risks
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] Release note makes sense to a user of the library
- [x] Author has acknowledged and discussed the performance implications
of this PR as reported in the benchmarks PR comment
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

(cherry picked from commit a1a0ea7)
@github-actions github-actions bot requested a review from a team as a code owner May 29, 2024 16:41
@github-actions github-actions bot added the changelog/no-changelog A changelog entry is not required for this PR. label May 29, 2024
@Yun-Kim Yun-Kim added changelog/no-changelog A changelog entry is not required for this PR. and removed changelog/no-changelog A changelog entry is not required for this PR. labels May 29, 2024
@Yun-Kim Yun-Kim enabled auto-merge (squash) May 29, 2024 16:41
@datadog-dd-trace-py-rkomorn
Copy link

Datadog Report

Branch report: backport-9398-to-2.9
Commit report: e429052
Test service: dd-trace-py

✅ 0 Failed, 2798 Passed, 737 Skipped, 56m 40.05s Total duration (27m 12.82s time saved)

@Yun-Kim Yun-Kim merged commit 03e2c2d into 2.9 May 29, 2024
80 of 83 checks passed
@Yun-Kim Yun-Kim deleted the backport-9398-to-2.9 branch May 29, 2024 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant