#dominoforever | Product Ideas Portal

 

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

Expand the default size limitation of console log in Domino server

The default size limitation of console log (console.log) in Domino server is 10 MB. If the size exceeds 10MB, the contents of the log will be cycled and the old contents will be deleted.

However, with the amount of features available on Domino servers these days, 10MB would soon be reached. When something goes wrong with the Domino server, if we try to check the past status in console log, we may not be able to see errors and such because they have already been deleted. Changing the size limit after a problem by Console_Log_Max_Kbytes parameter has occurred is already too late to investigate.

So, we want to expand the default size of console log in Domino server. (ex. 1GB)
Since HDDs and SSDs have large enough capacity these days, there should be no problem even if the default size is large.

  • Guest
  • Dec 8 2021
  • Needs Review
  • Attach files
  • Guest commented
    28 Dec, 2021 05:23am

    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.

  • Guest commented
    10 Dec, 2021 11:45am

    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