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() #9398

Merged
merged 2 commits into from
May 28, 2024

Conversation

Yun-Kim
Copy link
Contributor

@Yun-Kim Yun-Kim commented May 27, 2024

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

@Yun-Kim Yun-Kim added the changelog/no-changelog A changelog entry is not required for this PR. label May 27, 2024
@Yun-Kim Yun-Kim force-pushed the yunkim/llmobs-patch-only-llms branch from a72aa9e to dee98a9 Compare May 27, 2024 21:08
@Yun-Kim Yun-Kim force-pushed the yunkim/llmobs-patch-only-llms branch from dee98a9 to 1a1ae20 Compare May 27, 2024 21:33
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented May 27, 2024

Datadog Report

Branch report: yunkim/llmobs-patch-only-llms
Commit report: 20323fd
Test service: dd-trace-py

✅ 0 Failed, 2397 Passed, 1090 Skipped, 57m 36.68s Total duration (29m 32.84s time saved)

@Yun-Kim Yun-Kim marked this pull request as ready for review May 28, 2024 14:48
@Yun-Kim Yun-Kim requested a review from a team as a code owner May 28, 2024 14:48
@Yun-Kim Yun-Kim changed the title feat(llmobs): Modify integration patch behavior in llmobs.enable() feat(llmobs): modify integration patch behavior in llmobs.enable() May 28, 2024
@Yun-Kim Yun-Kim enabled auto-merge (squash) May 28, 2024 18:10
@datadog-datadog-prod-us1
Copy link

Software Composition Analysis

We found vulnerabilities in the following libraries (compared 20323fd against 307fb17):

@Yun-Kim Yun-Kim merged commit a1a0ea7 into main May 28, 2024
111 of 114 checks passed
@Yun-Kim Yun-Kim deleted the yunkim/llmobs-patch-only-llms branch May 28, 2024 18:45
github-actions bot pushed a commit that referenced this pull request May 29, 2024
…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)
Yun-Kim added a commit that referenced this pull request May 29, 2024
…ackport 2.9] (#9434)

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

- [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)

Co-authored-by: Yun Kim <35776586+Yun-Kim@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.9 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.

None yet

2 participants