Reduce the log level of 'request limit exceeded' messages#2788
Merged
Kludex merged 2 commits intoKludex:mainfrom Feb 15, 2026
Merged
Reduce the log level of 'request limit exceeded' messages#2788Kludex merged 2 commits intoKludex:mainfrom
Kludex merged 2 commits intoKludex:mainfrom
Conversation
Kludex
approved these changes
Feb 15, 2026
Merged
theseriff
pushed a commit
to theseriff/uvicorn
that referenced
this pull request
Mar 9, 2026
Co-authored-by: Shahar Evron <shahar@DS-shahar-MBP.local>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
This PR is a follow-up on #2782
In #2430 a WARNING level message was added when the defined
--limit-max-requestslimit is reached and the process is restarted.IMHO this should be an INFO level message, as it doesn't indicate any abnormal or potentially broken behavior, but in fact a 100% normal behavior. Using WARNING level message really pollutes the logs in high traffic servers, and the only way to silence these messages is to filter them in the logger configuration based on the content of the message, which is far from ideal.
This PR only changes the level of the message from WARNING to INFO.
Checklist