Zulu 2/Logging Properties

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
(Step 3)
 
(4 intermediate revisions by 3 users not shown)
Line 24: Line 24:
 
====Primary Logging Levels====
 
====Primary Logging Levels====
  
 +
 +
* <code>FINEST</code>
 +
* <code>FINER</code>
 +
* <code>FINE</code>
 +
* <code>CONFIG</code>
 
* <code>INFO</code>
 
* <code>INFO</code>
 
* <code>WARNING</code>
 
* <code>WARNING</code>
* <code>ERROR</code>
 
 
* <code>SEVERE</code>
 
* <code>SEVERE</code>
  
To change the logging level, simply change the last word to match the max level you want to log.
+
To change the logging level, simply change the last word to match the level you want to log. FINEST is the most granular and verbose level and will log everything. SEVERE is the least verbose and will log only SEVERE level errors.
 
+
 
=====Example=====
 
=====Example=====
<code>1catalina.org.apache.juli.FileHandler.level = ERROR</code>
+
<code>1catalina.org.apache.juli.FileHandler.level = SEVERE</code>
  
 
Once you've set it to the level you'd like, go ahead and save the file.
 
Once you've set it to the level you'd like, go ahead and save the file.
Line 38: Line 41:
 
===Step 3===
 
===Step 3===
  
Restart Zulu in the '''360Works Admin Tool''' to begin logging at the level you've set.
+
Restart Zulu in the '''360Works Admin Tool''' to begin logging at the level you've set. This utility is found in /Applications on Mac or C:\Program Files\360Works on Windows
  
 
===Reasons to change logging level===
 
===Reasons to change logging level===
  
 
For a single-instance of Zulu changing the level will likely be unnecessary, but for multiple instances (which you will need to change the logging properties for each instance) your log file can build up, fast. Changing the log level can save disk space on your system, especially if you have Zulu refreshing at a short interval.
 
For a single-instance of Zulu changing the level will likely be unnecessary, but for multiple instances (which you will need to change the logging properties for each instance) your log file can build up, fast. Changing the log level can save disk space on your system, especially if you have Zulu refreshing at a short interval.

Latest revision as of 16:30, 22 March 2021

If you're running into large log files or just want to limit the size of your log files in general, you may edit the logging properties in Zulu.

Contents

[edit] Step 1

Navigate to the following directory for your respective systems and open up logging.properties in your text editor of choice.

[edit] Windows

C:\Program Files\360Works\Application\webapps\zulu\WEB-INF\classes\

[edit] Mac

Library/360Works/Application/webapps/zulu/WEB-INF/classes/

[edit] Other

If you cannot find either directory, you may have a custom installation of Zulu. Please contact the system administrator who installed Zulu for assistance finding this installation location.

[edit] Important

If you did a hosting provider installation of zulu, the "zulu" in the filepath (the bold large text) will instead be the name you gave to your hosting provider installation.

[edit] Step 2

With logging.properties open, do a search for the 1catalina.org.apache.juli.FileHandler.level property. You want to change the text after the property to the level you want to log. By default it is INFO, please revert your logging level to INFO if you require support.

[edit] Primary Logging Levels

  • FINEST
  • FINER
  • FINE
  • CONFIG
  • INFO
  • WARNING
  • SEVERE

To change the logging level, simply change the last word to match the level you want to log. FINEST is the most granular and verbose level and will log everything. SEVERE is the least verbose and will log only SEVERE level errors.

[edit] Example

1catalina.org.apache.juli.FileHandler.level = SEVERE

Once you've set it to the level you'd like, go ahead and save the file.

[edit] Step 3

Restart Zulu in the 360Works Admin Tool to begin logging at the level you've set. This utility is found in /Applications on Mac or C:\Program Files\360Works on Windows

[edit] Reasons to change logging level

For a single-instance of Zulu changing the level will likely be unnecessary, but for multiple instances (which you will need to change the logging properties for each instance) your log file can build up, fast. Changing the log level can save disk space on your system, especially if you have Zulu refreshing at a short interval.

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox