-
Notifications
You must be signed in to change notification settings - Fork 536
feat(llmobs): capture inline base64 images for OpenAI chat completions and responses #19690
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
Open
joizddog
wants to merge
1
commit into
main
Choose a base branch
from
jose/mlob-6408-openai-image-parts
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 29 additions & 0 deletions
29
releasenotes/notes/llmobs-openai-image-parts-edf32dd7ad1d69db.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| --- | ||
| features: | ||
| - | | ||
| LLM Observability: The OpenAI integration now captures inline base64 images from message content | ||
| as ``image_parts`` on LLM span messages, for both Chat Completions and the Responses API, so | ||
| image inputs render in LLM Observability. This also applies to the OpenAI Agents SDK and to the | ||
| LiteLLM integration, which share the same message extraction. Images referenced by a remote URL | ||
| or ``file_id`` are not fetched and keep their existing text reference. A single inline image | ||
| whose base64 payload exceeds 4 MiB is left as an ``[image omitted: too large]`` marker instead. | ||
| Note that this budget is per image, not per request: several inline images (or an image | ||
| alongside inline audio) can still take a span event past the 5 MB per-event limit, at which | ||
| point the event's input and output are replaced with a placeholder. To stop image bytes from | ||
| being recorded, register a span processor with ``LLMObs.register_processor`` and remove the | ||
| ``image_parts`` key from the messages on ``span.input``. | ||
| fixes: | ||
| - | | ||
| LLM Observability: Fixes an issue where an inline base64 image sent in message content to the | ||
| OpenAI Responses API (including through the OpenAI Agents SDK) was recorded as the entire base64 | ||
| data URL inside the message text, producing unreadable multi-megabyte span content. | ||
| - | | ||
| LLM Observability: Fixes an issue where an inline base64 image passed as a reusable-prompt | ||
| variable to the OpenAI Responses API was recorded as the entire base64 data URL on the span. | ||
| Such a variable is now recorded as ``[image]``; remote URL and ``file_id`` references are | ||
| unchanged. | ||
| - | | ||
| LLM Observability: Fixes an issue where OpenAI Responses API image-generation results and | ||
| computer-use screenshots were recorded as a stringified dump of the whole response item, which | ||
| embedded the image's base64 payload in the output message. They are now recorded as an | ||
| ``[image]`` marker, or as the screenshot's URL when it is a remote reference. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update the LLMObs integration skill alongside this new extraction pattern:
.claude/skills/llmobs-integrations/SKILL.mdcurrently demonstrates onlyAudioPart, while itsreferences/implementation-guide.mdmessage-extraction section documents only audio attachments. Leaving both references unchanged means future integration work will miss the newImagePartcapture and size-guard conventions.AGENTS.md reference: AGENTS.md:L19-L19
Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skill file update remains blocked by classifier restrictions