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
Use the default settings for Logging{Client,Service}
's default fact…
#2855
Conversation
…ory methods Motivation: So far, `Logging{Client,Service}.newDecorator()` had different settings than `Logging{Client,Service}.builder().newDecorator()` due to backward compatibility. It's time to change this in favor of consistency. Modifications: - Change `Logging{Client,Service}.newDecorator()` to use its builder's default settings. - `TRACE` level logging for successful requests and responses. - `WARN` level logging for failed requests and responses`. Result: - Consistency - Fixes line#2696
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
By the way, is |
I don't remember but |
Actually, I'm leaning towards |
Related work: The default log level of Spring's CommonsRequestLoggingFilter is |
Let me change the default level from |
Codecov Report
@@ Coverage Diff @@
## master #2855 +/- ##
============================================
- Coverage 72.83% 72.72% -0.11%
- Complexity 12167 12168 +1
============================================
Files 1079 1080 +1
Lines 47283 47321 +38
Branches 5896 5896
============================================
- Hits 34438 34415 -23
- Misses 9817 9887 +70
+ Partials 3028 3019 -9 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still LGTM
line#2855) …ory methods Motivation: So far, `Logging{Client,Service}.newDecorator()` had different settings than `Logging{Client,Service}.builder().newDecorator()` due to backward compatibility. It's time to change this in favor of consistency. Modifications: - Change the default logging level for successful requests and responses from `TRACE` to `DEBUG`. - Change `Logging{Client,Service}.newDecorator()` to use its builder's default settings. - `DEBUG` level logging for successful requests and responses. - `WARN` level logging for failed requests and responses`. Result: - Consistency - Fixes line#2696 - (Breaking) The default logging level for successful requests and response has been changed: - `INFO` to `DEBUG` for `Logging{Client,Service}.newDecorator()` - `TRACE` to `DEBUG` for `Logging{Client,Service}Builder`
…ory methods
Motivation:
So far,
Logging{Client,Service}.newDecorator()
had different settingsthan
Logging{Client,Service}.builder().newDecorator()
due to backwardcompatibility. It's time to change this in favor of consistency.
Modifications:
from
TRACE
toDEBUG
.Logging{Client,Service}.newDecorator()
to use its builder'sdefault settings.
DEBUG
level logging for successful requests and responses.WARN
level logging for failed requests and responses`.Result:
has been changed:
INFO
toDEBUG
forLogging{Client,Service}.newDecorator()
TRACE
toDEBUG
forLogging{Client,Service}Builder