Logging

Transformer can log many aspects of its operation, to help you check that it’s running correctly and pinpoint the source of any problems arising.

Because Transformer is a DataSource application, it comes with the standard DataSource logging facilities built-in. It also produces a number of subsidiary logs that are dedicated to particular Transformer modules.

Here’s a summary of all the log files that Transformer can create, with links to the configuration items that define the log files and control the amount of detail logged.

Log type Default log filename Related configuration items

Event log

The standard DataSource event log

transformer.log

event-log

log-level

add-log

and others

in DataSource Logging configuration.

Packet log

The standard DataSource packet log

packet-transformer.log

datasrc-pkt-log

in DataSource peers configuration (part 2)

Pipeline activity log

The log file in which pipeline messages are recorded.

pipeline.log

logfile

log-level

pipeline-logflags

add-pipeline: log-flags

in Pipeline configuration.

Cluster log

The Cluster module’s log

cluster.log

logfile

log-level

in Clustering configuration

Cluster packet log

The log file in which message packets passed between a Transformer and other nodes in the Transformer cluster are recorded.

(none)

cluster-packet-logfile

in Clustering configuration

Java module log

One log file is produced for each Java module loaded into Transformer

<Java-module-name>.log

For example, jtm.log

module-logfile

log-level

in Java Transformer Module configuration

Thread queue sizes log

The log file in which the sizes of the thread queues are recorded.

(none)

threads-queue-report-logfile

threads-queue-report-period

in Pipeline threads configuration

Persistence event log

The log file in which events about persisting data are recorded.

persistence.log

logfile

log-level

in Persistence configuration

See also: