Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I would prefer log mirroring to be the default, with a default log size of 100 MB. Log files much bigger than 100 MB are cumbersome to work with in my experience. Typically you only have notepad available on Windows servers and it struggles with larger files.
I know enough to know that if I had set those parameters in advance, I would not have this problem.
However, in reality, customers rarely set such parameters in advance, and only notice them after a problem occurs and logs are circulated.
So, even if there is no action to pre-set such a parameter, the default size of the console log should be large from the beginning.
You realize you can set a larger size and use mirror logging? That way you never run into these issues.
Check out these settings:
CONSOLE_LOG_MAX_KBYTES=102400
CONSOLE_LOG_MIRROR=1
CONSOLE_LOG_ENABLED=1
RETAIN_MIRROR_LOGS=1
Search for Mirror Logging in HCL documentation