• Find a Logger of Interest
• Change Logging Level
• Logger Notes
• Troubleshoot with Loggers

Find a Logger of Interest

• Select > Site > Admin Console.
• Under Diagnostics, click Loggers.

• Find a specific logger by typing ahead (any portion of the name) to narrow the list.
• If you don't see an expected logger listed here, it may mean the relevant class has not yet been initialized or loaded by the VM by being called at least once.
• Use the Show Level dropdown to narrow the list to all loggers at a given level:
• INFO
• WARN
• ERROR
• FATAL
• DEBUG
• TRACE
• ALL
• OFF

Change Logging Level

Click the value in the Level column for a specific logger to reveal a dropdown menu for changing its current level. Select a new level and click elsewhere on the page to close the selector. The logger will immediately run at the new level until the server is restarted (or until its level is changed again).

For example, while investigating an issue you may want to set a particular logging path to DEBUG to cause that component to emit more verbose logging. Typically, your Account Manager will suggest the logger(s) and level to set.

Another way to use the adjustability of logging is to lower logging levels to limit the growth of the labkey.log file. For example, if your log is filling with INFO messages from a given logger, and you determine that these messages are benign, 'raising' the threshold for messages being written to the log (such as to ERROR) will reduce overall log size. However, this also means that information that could help troubleshoot an issue will not be retained.

Learn more about logger file sizes in this topic: Troubleshoot Installation and Configuration

Logger Notes

Some loggers provide a brief note about what specific actions or information they will log. Use this information to guide you in raising (or lowering) logging levels as your situation requires.

Troubleshoot with Loggers

If you want enhanced debug logging of a specific operation, the general process will be:

1. Changing the relevant logging level(s) to "DEBUG" as described above.
2. Optionally select Admin Console > Caches > Clear Caches and Refresh.
3. Repeat the operation you wanted to have logged at the debugging level.
4. Check the labkey.log to see all the messages generated by the desired logger(s).
5. Remember to return your logger to the previous level after resolving the issue; otherwise the debugging messages will continue to fill the labkey.log file.

Related Topics

• Admin Console
• Troubleshoot LabKey Server
• Troubleshoot Installation and Configuration