-
Notifications
You must be signed in to change notification settings - Fork 427
fix(logger): warn customers when the ALC log level is less verbose than log buffer #6509
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6509 +/- ##
===========================================
- Coverage 96.16% 96.14% -0.03%
===========================================
Files 243 243
Lines 11836 11844 +8
Branches 881 885 +4
===========================================
+ Hits 11382 11387 +5
- Misses 358 359 +1
- Partials 96 98 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Hey @anafalcao! Thanks a lot for this PR, please just check my comments!
tests/functional/logger/required_dependencies/test_powertools_logger_buffer.py
Outdated
Show resolved
Hide resolved
|
…an log buffer (#6509) * fix(logger): warn customers when the ALC log level is less verbose than log buffer * change flush buffer warning * mypy * mypy * mypy * fix logger * change flush buffer warn * check buffer config --------- Co-authored-by: Leandro Damascena <[email protected]>
Issue number: #6440
Summary
When the Advanced Logging Control is less verbose than the Logger Log buffer, buffered logs will not be visible. This PR adds a warning that is emitted when this scenario is detected.
There's an existing warning message if the ALC Log Level is less verbose than the Logger Log Level.
Changes
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.