Skip to content

Feat add retention config #10815

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

Merged
merged 8 commits into from
May 15, 2025
Merged

Feat add retention config #10815

merged 8 commits into from
May 15, 2025

Conversation

jugaldb
Copy link
Collaborator

@jugaldb jugaldb commented May 14, 2025

Title

Init on setting retention period for spend logs

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

Copy link

vercel bot commented May 14, 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 15, 2025 1:14am

@@ -211,6 +212,7 @@ general_settings:
| enable_oauth2_proxy_auth | boolean | (Enterprise Feature) If true, enables oauth2.0 authentication |
| forward_openai_org_id | boolean | If true, forwards the OpenAI Organization ID to the backend LLM call (if it's OpenAI). |
| forward_client_headers_to_llm_api | boolean | If true, forwards the client headers (any `x-` headers) to the backend LLM call |
| maximum_retention_period | str | Used to set the max retention time for spend logs in the db, after which they will be auto-purged |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reading this over - can we make this more precise, e.g. maximum_spend_logs_retention_period?

It's more verbose but also more precise (i know exactly what it means when i read it)

@krrishdholakia
Copy link
Contributor

Hey @jugaldb i can't tell why your diff with config_settings.md is so large. Can you please resolve it - it's blocking merge

@krrishdholakia krrishdholakia merged commit a754a25 into main May 15, 2025
10 of 11 checks passed
@krrishdholakia krrishdholakia deleted the feat_add_retention_config branch May 15, 2025 01:16
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