	A log controller - can be a "category" or a "location". Categories are used for "logging" and represent problem areas such as network, database, security, user interface, etc. Identified by a slash-separated ('/') path of names, prefixed with an additional slash. Locations are used for "tracing" and correspond to places in the development components. Identified by a dot-separated ('.') path of names, which is often the name of the respective java package.
	A placeholder for a non-existing controller. (It is not required that the parent of an existing controller is also existing, so some nodes in the tree are "hollow".)
	"Apply" button. Commits the changes you have made.
	Enable/disable SQL trace.
	Archiving - creates a zip archive containing log files which correspond to selected log destinations.
	Switch between simple and advanced mode. In advanced mode you can edit the log destinations, log formatters, log controllers' min and max severities, and relative controllers. You can also add and remove controllers.

Fatal	Uncorrectable error conditions in program execution, which terminate the current application without fulfilling the desired task. The application is not usable anymore.
Error	Same as Fatal, but the application remains usable.
Warning	The application processing can and will proceed, but later follow-up activity by people responsible for the specific category is necessary to avoid error situations in the future. Information of how to solve the problem in the future.
Info	Informational text to record an event, which does not have and does not need any follow-up activity. It should help to understand the normal operation or could provide further information for later reviews, audits or investigations.
Path	Information for developers and support engineers to understand the execution flow of a program.
Debug	Information only valuable for developers to analyze the internal status of a program.

In order to assign a severity level to a subtree of controllers do the following: select the root of the subtree, change to the desired severity, click "Copy severity to subtree", then click "Apply" ().
"Reset to default" for a subtree simply traverses the subtree of existing controllers and restores the default severity for each of them. On the other hand, "Installation defaults" (in the toolbar above) replaces the entire log configuration, which may lead to creation and/or deletion of some controllers.