Logging, tracing, debugging, and profiling

Logging, tracing, debugging and profiling is carried out using the standard log4j facility. In addition, special logging categories are available:

Category	Level	Description
dataporter.config	INFO	Prints some details of the configuration such as available pool, source, or sink instances.
	DEBUG	This level is used for additional configurational information. In particular, it is used for debugging if the whole data context is dumped in case of an exception. This information can be used to visualize the data causing the exception.
dataporter.statistics	INFO	Prints a basic statistics summary.
	DEBUG	Prints the statistics of every component individually.
dataporter.timing	INFO	Prints some basic timing information on entity level.
	DEBUG	Prints detailed timing information on function level.
dataporter.profile	INFO	Prints timing information of every component.
	DEBUG	Prints timing information of every component, including sub-operations, such as SQL queries or WS calls.
dataporter.simulate	DEBUG	Prints detailed simulation results.