Skip to content

Conversation

jackshirazi
Copy link
Contributor

upstream agent now 2.18.1 (needs some small internal test changes)
this distributions openai-client is turned off, leaving the upstream openai instrumentation to do the work (needed a couple of tests disabled)

@jackshirazi jackshirazi requested a review from a team as a code owner August 7, 2025 13:41
Copy link

github-actions bot commented Aug 7, 2025

🔍 Preview links for changed docs

Copy link
Contributor

@theletterf theletterf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some nits

@theletterf
Copy link
Contributor

The idea is that the issue will be solved, right? Otherwise, we might have to mark the update as a breaking change where relevant...

jackshirazi and others added 4 commits August 8, 2025 13:03
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
@jackshirazi
Copy link
Contributor Author

The idea is that the issue will be solved, right? Otherwise, we might have to mark the update as a breaking change where relevant...

This will be a permanent breaking change. If we merge this, I'll open PRs for the docs for the next version

Copy link
Member

@SylvainJuge SylvainJuge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I think we just need to have an issue that describes the follow-up tasks for the removal of openai.

Comment on lines +50 to +51
// OTEL_INSTRUMENTATION_OPENAI=false
// OTEL_INSTRUMENTATION_OPENAI_CLIENT=true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the difference between those two variables ? are there two instrumentations or at least two config options in upstream ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the upstream one uses OTEL_INSTRUMENTATION_OPENAI, while our implementation uses OTEL_INSTRUMENTATION_OPENAI_CLIENT. If the upstream one had used the same var, it wouldn't have been a breaking change and we could have just removed our implementation

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.RegisterExtension;

@Disabled
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand correctly disabling those tests is required because now the upstream instrumentation is used. Do we already have an issue that describes the deprecation and removal steps ? Aligning the removal with the update to 3.x upstream seems a good option as it already forces to do a new major.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issue opened yet, I will open when this is merged

@jackshirazi jackshirazi merged commit 25bd5f2 into elastic:main Aug 21, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants