Setting the Logging Detail Level for Stratus Cloud Workload Services

After installing Stratus Cloud Workload Services, optionally configure the logging detail level and log file behavior in the Stratus appliance.

To set the logging detail level and behavior for Workload Services:

1. Log on to the Stratus appliance as the cloud-user and execute the su command to become the root user (or be prepared to use sudo to run commands as root).

2. Open the /opt/jetty/resources/CloudMgmtExt.properties file in a text editor and modify the API and Orchestrator logging levels as shown here in red. By default, the logging detail level is set to debug, but you can specify other levels as described in the file:

   #### LOGGING LEVEL (OPTIONAL) Default : debug if not found

   #POSSIBLE VALUES : DEBUG/INFO/WARN/ERROR/FATAL

   #fatal: shows messages at a FATAL level only

   #error: Shows messages classified as ERROR and FATAL

   #warning: Shows messages classified as WARNING, ERROR, and FATAL

   #info: Shows messages classified as INFO, WARNING, ERROR, and FATAL

   #debug: Shows messages classified as DEBUG, INFO, WARNING, ERROR, and FATAL

   #trace : Shows messages classified as TRACE,DEBUG, INFO, WARNING, ERROR, and FATAL

   # APPLIES FOR BOTH API AND ORCHESTRATOR

   cloud.mgmt.api.logging.level=info

   cloud.mgmt.orchestrator.logging.level=info

   cloud.mgmt.presentation.api.logging.level=info

3. Save and close the CloudMgmtExt.properties file.

4. Open the /opt/jetty/resources/log4j4OrchExt.xml file in a text editor and modify the values shown here in red to set the number of log files to back up and the maximum log file size before the system rolls over to a new log file:

   # APPLIES FOR BOTH API AND ORCHESTRATOR

   <param value="20" name="MaxBackupIndex" />
   <param value="10MB" name="MaxFileSize" />
5. Save and close the log4j4OrchExt.xml file.
6. Restart Jetty by entering the command service jetty restart.