Avoid Logging 4XX Status Codes as Errors #1279
Labels
enhancement
New feature or request
Service
Related to external http, grpc communciation , middlewares etc.
Problem
Currently, 4XX HTTP status codes are logged as errors, which can clutter the logs and mislead monitoring systems. Client-side issues should not be considered server errors.
Expected Behavior
Proposed Solution
The text was updated successfully, but these errors were encountered: