Skip to content

Conversation

@NANDINI-star
Copy link
Contributor

Filter keys hash and key alias on logs table

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🆕 New Feature

Changes

  • Create one unified path that builds a single dynamic query with flexible WHERE conditions and pagination included, so all filters (api_key, key_alias, status, date, model, spend, etc.) are applied consistently.

Please check the working feature here(i couldn't figure how to add logs data with key alias value, so i couldn't test but it should work without any problems): https://drive.google.com/file/d/1h_jSr_jTw0TItQbWXpEUHaV3Sep1jflt/view?usp=sharing

@NANDINI-star NANDINI-star requested a review from ishaan-jaff May 10, 2025 12:47
@vercel
Copy link

vercel bot commented May 10, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
litellm ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 10, 2025 3:05pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants