-
Notifications
You must be signed in to change notification settings - Fork 64
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
feat: introduce maxEntrySize, for enabling error message truncation #607
Conversation
Codecov Report
@@ Coverage Diff @@
## master #607 +/- ##
==========================================
- Coverage 97.21% 96.84% -0.37%
==========================================
Files 10 10
Lines 431 444 +13
Branches 55 60 +5
==========================================
+ Hits 419 430 +11
- Partials 12 14 +2
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.
Approved with one suggestion
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.
LGTM w/ nits
What are the units of maxEntrySize? |
@xtellurian I assume you sorted this out but for anyone else, it's bytes |
introduces the configuration setting
maxEntrySize
which, if set, will make a best effort to truncate text log entries, such that they don't result in an exception, see:https://cloud.google.com/logging/quotas
Note: as follow up, we should set this option to
256,000
on logging-bunyan, and logging-winston.fixes #427