You can add loggers to the root log and set their logging level to keep track of errors or some activities.
Loggers combine closely related log items into an entry in the logging library. Logger output is directed to the main or root log file, that is deployserver.out.
Changing log configuration enables you to debug logging for specific loggers. Loggers can be configured with an easy to use UI.
Open the Logging page by clicking
.Loggers are listed in hierarchical order. The first one is the root logger, which is indicated by an
*in the UI. It typically has no name in the logging library. The other default loggers and log classes are as follows:
Each logger has a level drop-down that allows you to change the logging level. The following log level types are available:
com.sun.jersey.server.impl.application.WebApplicationImpl com.sun.jersey.spi.container.ContainerResponse com.urbancode.air.diagnostics com.urbancode.air.vc com.urbancode.container.tomcat com.urbancode.ds com.urbancode.encryption.keystore net.schmizz org.apache.tomcat org.hibernate.cache.ReadWriteCache org.hibernate.engine.jdbc.spi.SqlExceptionHelper org.hibernate.orm.deprecation com.urbancode.ds.cleanup
- To edit multiple loggers simultaneously, select the loggers from the selection column, click Bulk Actions, set the level as required, and save your changes.
- To add a logger, click Add Logger, specify the logger name, it's logging level, and confirm your changes.
- To delete a custom logger use the actions column or to delete multiple loggers, use Bulk Actions. The root and default loggers cannot be deleted. Removing a logger reverts the logger to the logging level defined by its superior in the hierarchy.