[SERVER-30386] Rename maxLogSizeKB parameter to maxLogLineKB Created: 28/Jul/17  Updated: 08/Jan/24  Resolved: 14/Aug/17

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 3.4.0
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Kevin Pulo Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17358 Add flag to customize maxLogLine when... Closed
Backwards Compatibility: Minor Change
Participants:

 Description   

The server parameter named "maxLogSizeKB" has the connotation of being the "max‍imum size (in KB) of the/a log". Without any additional context most people will interpret "log" as meaning "log file" (aided by the ".log" extension of these files), rather than "log line". Thus people may incorrectly expect this parameter to be related to logfile rotation, as opposed to the summarisation of very long individual log lines.

As such we should consider renaming "maxLogSizeKB" to "maxLogLineKB".



 Comments   
Comment by Kevin Pulo [ 14/Aug/17 ]

After some discussion it was determined that the change management costs of doing this would be too high.

Generated at Thu Feb 08 04:23:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.