[SERVER-17358] Add flag to customize maxLogLine when logging large lines Created: 23/Feb/15 Updated: 15/May/18 Resolved: 20/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Travis Redman | Assignee: | Waley Chen |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Sprint: | Platforms 2016-09-19, Platforms 2016-10-10 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
The logger truncates log messages larger than 10k by printing the first ~3k bytes and last ~3k bytes and printing a "........" in the center. This limit seems arbitrary and would be useful if we could override it. We have customers submitting very large queries (huge $in: [] clauses for example) and although not ideal, the query contents are useful to us. The ellipses often break our query parser when doing log analysis. It looks like a simple enough change - we would just need to switch maxLogLine from a const to some flag-driven value.
|
| Comments |
| Comment by Kevin Pulo [ 06/Jul/17 ] |
|
The added parameter is called maxLogSizeKB. |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'username': u'WaleyChen', u'name': u'Waley Chen', u'email': u'waleycz@gmail.com'}Message: |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: Revert " This reverts commit 7c6c92e3cd514a156a49ae9e5139ea66d324c004. |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'username': u'WaleyChen', u'name': u'Waley Chen', u'email': u'waleycz@gmail.com'}Message: |