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
The Agents SDK currently provides no way to retrieve traces after they’ve been sent to OpenAI’s servers, forcing users to resort to scraping the dashboard if they didn’t persist them elsewhere. Nor does there seem to be an export button in the platform UI. While custom tracing processors offer a solution for future trace storage, there should be a supported way to access historical traces that were already ingested but not externally persisted.
The text was updated successfully, but these errors were encountered:
You can use custom tracing processors to send your traces to anywhere else from OpenAI's backend. So you can use them anytime anywhere.
Also Responses API keeps the responses for 30 days. I'm not sure but there may be a limit for traces, too. So storing your traces in your own db may be helpful.
@paulsengh makes sense. If there were an export button - how many traces would you want to export? e.g. one page at a time? Jus trying to get a sense for how you'd use an API and/or export button
The Agents SDK currently provides no way to retrieve traces after they’ve been sent to OpenAI’s servers, forcing users to resort to scraping the dashboard if they didn’t persist them elsewhere. Nor does there seem to be an export button in the platform UI. While custom tracing processors offer a solution for future trace storage, there should be a supported way to access historical traces that were already ingested but not externally persisted.
The text was updated successfully, but these errors were encountered: