Merge branch 'owls-131301-add-nmprops-env' into 'release/4.2'

add node manager logging variables

See merge request weblogic-cloud/weblogic-kubernetes-operator!5006

Author: rjeberhard

documentation/site/content/managing-domains/domain-resource.md

@@ -243,6 +243,14 @@ You can use the following environment variables to specify JVM memory and JVM op
 * `PRE_CLASSPATH`: Path(s) that are *prepended* to the WebLogic Server system classpath; delimit multiple paths with a colon `:`.
 * `CLASSPATH`: Path(s) that are *appended* to the WebLogic Server system classpath; delimit multiple paths with a colon `:`.
 
+### Node Manager environment variables
+
+You can use the following environment variables to specify the logging files limit. 
+
+* `NODEMGR_LOG_FILE_MAX`: Maximum size of the Node Manager Log specified as an integer. When this limit is reached, a new log file is started. Default: 0, no limit.
+* `NODEMGR_LOG_LEVEL`: Severity level of logging used for the Node Manager log. Node Manager uses the standard logging levels from the java.util.logging.level package. Default: FINEST.
+* `NODEMGR_LOG_COUNT`: Maximum number of log files to create when LogLimit is exceeded. Default: 1.
+
 **NOTES**:
 
 * The following behavior occurs depending on whether or not `NODEMGR_JAVA_OPTIONS` and `NODEMGR_MEM_ARGS` are defined:

documentation/site/content/managing-domains/manage-domains.md

@@ -163,6 +163,12 @@ Be aware of the following important considerations for WebLogic domains running
 
     For more information, see [JVM memory and Java option environment variables]({{< relref "/managing-domains/domain-resource#jvm-memory-and-java-option-environment-variables" >}}).
 
+* _Node Manager environment variables:_ You can use the following environment variables to specify the logging files limit.
+
+    * `NODEMGR_LOG_FILE_MAX`: Maximum size of the Node Manager Log specified as an integer. When this limit is reached, a new log file is started. Default: 0, no limit.
+    * `NODEMGR_LOG_LEVEL`: Severity level of logging used for the Node Manager log. Node Manager uses the standard logging levels from the java.util.logging.level package. Default: FINEST.
+    * `NODEMGR_LOG_COUNT`: Maximum number of log files to create when LogLimit is exceeded. Default: 1.
+
 
 The following features are **not** certified or supported in this release:
 

operator/src/main/resources/scripts/startNodeManager.sh

@@ -27,7 +27,11 @@
 #                          ${DOMAIN_UID}/${SERVER_NAME}_nodemanager.out
 #                       Default:
 #                          Use LOG_HOME.  If LOG_HOME not set, use NODEMGR_HOME.
-#   NODEMGR_LOG_FILE_MAX = max NM .log and .out files to keep around (default=11)
+#   NODEMGR_LOG_FILE_MAX = Maximum size of the Node Manager Log specified as an integer.
+#      When this limit is reached, a new log file is started. default 0, no limit.
+#   NODEMGR_LOG_LEVEL =Severity level of logging used for the Node Manager log. Node Manager uses the standard
+#      logging levels from the java.util.logging.level package. default FINEST.
+#   NODEMGR_LOG_COUNT = Maximum number of log files to create when LogLimit is exceeded. default 1.
 #
 #   ADMIN_PORT_SECURE = "true" if the admin protocol is secure. Default is false
 #
@@ -64,6 +68,9 @@ stm_script=${WL_HOME}/server/bin/startNodeManager.sh
 
 SERVER_NAME=${SERVER_NAME:-introspector}
 ADMIN_PORT_SECURE=${ADMIN_PORT_SECURE:-false}
+NM_LOG_LIMIT=${NODEMGR_LOG_FILE_MAX:-0}
+NM_LOG_LEVEL=${NODEMGR_LOG_LEVEL:-FINEST}
+NM_LOG_COUNT=${NODEMGR_LOG_COUNT:-1}
 
 trace "Starting node manager for domain-uid='$DOMAIN_UID' and server='$SERVER_NAME'."
 
@@ -241,9 +248,9 @@ cat <<EOF > ${nm_props_file}
   LogToStderr=true
   LogFormatter=weblogic.nodemanager.server.LogFormatter
   LogAppend=true
-  LogLimit=0
-  LogLevel=FINEST
-  LogCount=1
+  LogLimit=${NM_LOG_LIMIT}
+  LogLevel=${NM_LOG_LEVEL}
+  LogCount=${NM_LOG_COUNT}
 
 EOF