Specifying the verbosity of the log

3.7 Specifying the verbosity of the log

The <logger> tags describe the different log levels that can be changed according to the Java packages of the source code. The list that follows describes the packages used in the default configuration. Each logger tag has an associated value that indicates the verbosity level.

Value	Description
com.cri	This is the general package for all Viewpoint server code. This will log all server interaction with the Viewpoint Web server.
com.cri.security	This is the logger for all security packages. This is important for authentication and authorization testing.
com.ace	This is the logger for external Java API classes. This includes Java code that has been validated for external customer consumption. Classes include MoabJob, MoabNode, Reservation, and so forth. See the Moab Java API for more information.
com.Moab	This is the logger for internal Java API classes. Classes include VPCs, low-level Moab consumption, etc. This is the logger that shows what Moab commands are sent and the associated output.
Root Logger	This is the logger for everything other than the specified loggers. This is a catch-all for logging of the Tomcat server, Hibernate, the database connection pool, and other third-party libraries. Unless the packages are explicitly specified in a logger like the previous examples, the logging will fall into the root logger.

Value

Description

com.cri

This is the general package for all Viewpoint server code. This will log all server interaction with the Viewpoint Web server.

com.cri.security

This is the logger for all security packages. This is important for authentication and authorization testing.

com.ace

This is the logger for external Java API classes. This includes Java code that has been validated for external customer consumption. Classes include MoabJob, MoabNode, Reservation, and so forth. See the Moab Java API for more information.

com.Moab

This is the logger for internal Java API classes. Classes include VPCs, low-level Moab consumption, etc. This is the logger that shows what Moab commands are sent and the associated output.

Root Logger

This is the logger for everything other than the specified loggers. This is a catch-all for logging of the Tomcat server, Hibernate, the database connection pool, and other third-party libraries. Unless the packages are explicitly specified in a logger like the previous examples, the logging will fall into the root logger.

To specify the verbosity of the log

Open the log4j.xml file located in the Viewpoint home directory.

Locate the <logger> element that corresponds to the category for which you want to change the verbosity level. Categories are defined in the code comments.

Choose the <level value> according to what information you want to appear in the log.

The levels are cumulative, meaning that each level also logs the messages logged by levels hierarchically ordered below it. For example, if an administrator configures a logging level of info, method calls to logger.info(), logger.warn(), logger.error(), and logger.fatal() are also logged.

The following table offers a brief description of the various log4j verbosity levels:

Level	Definition
trace	All data
debug	Normal operations
info	Significant system events such as application initialization, logging initialization, and occurrence of rare global events
warn	Recoverable exceptions or unexpected state
error	Unrecoverable request exceptions or recoverable system errors
fatal	Unrecoverable system errors resulting in a crash of the application

To eliminate logging for a category altogether, comment out the entire section with  brackets, as in the following example:

<!-- Logger for Viewpoint server code
<logger name="com.cri" additivity="false">
<level value="info"></level>
<appender-ref ref="file"></appender-ref>
</logger>
-->