fix: change cost calculation logs from INFO to DEBUG level #12112
+95
−2
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.
Title
fix: change cost calculation logs from INFO to DEBUG level
Relevant issues
Part 2/2 of fix for #9815
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-unit
Type
🐛 Bug Fix
Changes
This PR changes cost calculation logs from INFO to DEBUG level to reduce log noise in production environments.
Problem
Cost calculation logs ("selected model name for cost calculation") were being emitted at INFO level, which is too verbose for production use. These logs should be debug-level information that's only shown when troubleshooting.
Solution
Changed
verbose_logger.info()
toverbose_logger.debug()
for:completion_cost()
functionbatch_cost_calculator()
functionTesting
Added tests in
test_cost_calculation_log_level.py
that verify:Test Output
This is part 2 of a 2-part fix. The first PR (#12111) addresses the root cause by making loggers respect the LITELLM_LOG environment variable.