DP log levels

This topic describes the log levels that can be set in the DP log4j.properties file.

The Data Processing logger is configured with the type of information written to log files, by specifying the log level. When you specify the type, the DP logger returns all messages of that type, as well as the messages that have a higher severity. For example, if you set the message type to WARN, messages of type FATAL and ERROR are also returned.

The DP log4j.properties file lists these four packages for which you can set a logging level:

log4j.rootLogger
log4j.logger.org.eclipse.jetty
log4j.logger.org.apache.spark.repl.SparkIMain$exprTyper
log4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter

You can change a log level by opening the properties file in a text editor and changing the level of any of the four packages. You use a Java log level from the table below. :

This example shows how you can manually change a log level setting:

log4j.rootLogger = FATAL, console, edpMain

In the example, the log level for the main logger is set to FATAL.

Logging levels

The log levels (in decreasing order of severity) are:

Java Log Level	ODL Log Level	Meaning
`OFF`	N/A	Has the highest possible rank and is used to turn off logging.
`FATAL`	`INCIDENT_ERROR`	Indicates a serious problem that may be caused by a bug in the product and that should be reported to Oracle Support. In general, these messages describe events that are of considerable importance and which will prevent normal program execution.
`ERROR`	`ERROR`	Indicates a serious problem that requires immediate attention from the administrator and is not caused by a bug in the product.
`WARN`	`WARNING`	Indicates a potential problem that should be reviewed by the administrator.
`INFO`	`NOTIFICATION`	A message level for informational messages. This level typically indicates a major lifecycle event such as the activation or deactivation of a primary sub-component or feature. This is the default level.
`DEBUG`	`TRACE`	Debug information for events that are meaningful to administrators, such as public API entry or exit points. You should not use this level in a production environment, as performance for DP jobs will be slower.

These levels allow you to monitor events of interest at the appropriate granularity without being overwhelmed by messages that are not relevant. When you are initially setting up your application in a development environment, you might want to use the DEBUG level to get most of the messages, and change to a less verbose level in production.