fix: clean arize-phoenix traces #16611
Merged
Conversation
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
|
@axiomofjoy is attempting to deploy a commit to the CLERKIEAI Team on Vercel. A member of the Team first needs to authorize it. |
|
|
axiomofjoy
force-pushed
the
clean-phoenix-traces
branch
from
e7e21c1 to
436461f
Compare
Contributor
|
@axiomofjoy can you share a screenshot of this working as expected on arize phoenix? |
Contributor
Author
|
busla
pushed a commit
to aproorg/litellm
that referenced
this pull request
Dec 4, 2025
* fix * clean * clean * clean * clean * clean * lint
busla
pushed a commit
to aproorg/litellm
that referenced
this pull request
Dec 4, 2025
* fix * clean * clean * clean * clean * clean * lint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Clean Arize-Phoenix traces
Previously, non-OpenInference spans were being emitted by the proxy server. Some of these spans have start time timestamps at the start of the epoch, which throws off our time range filtering. Most of our users care about the spans that are relevant to the LLM call, not other spans.
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🧹 Refactoring