Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
Accelerator
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading.
Please reload this page
.
DataDog
/
dd-trace-py
Public
Notifications
You must be signed in to change notification settings
Fork
536
Star
648
Code
Issues
102
Pull requests
184
Actions
Security and quality
1
Insights
Additional navigation options
Code
Issues
Pull requests
Actions
Security and quality
Insights
Files
Expand file tree
a528b617333b562b14a81af311448963bce73e06
Breadcrumbs
dd-trace-py
/
releasenotes
/
notes
/
llmobs-openai-image-parts-edf32dd7ad1d69db.yaml
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
29 lines (29 loc) · 1.99 KB
a528b61
Breadcrumbs
dd-trace-py
/
releasenotes
/
notes
/
llmobs-openai-image-parts-edf32dd7ad1d69db.yaml
Copy path
Top
File metadata and controls
Code
Blame
29 lines (29 loc) · 1.99 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
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.
You can’t perform that action at this time.