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.

Timestamps in log files

From version 7.1 of Transformer, the resolution of log-event timestamps has been increased from millisecond to microsecond granularity. This aligns Transformer with the trend within the financial industry towards the use of higher-resolution timestamps. For more information, see Timestamp resolution.

Event log

The standard DataSource event log.

Default file name: transformer.log

Configuration items: event-log, log-level, add-log, and others in DataSource Logging configuration.

Packet log

The standard DataSource packet log.

Default file name: packet-transformer.log

Pipeline activity log

Pipeline message log.

Default file name: pipeline.log

Configuration items: logfile, log-level, pipeline-logflags, and add-pipeline:log-flags in Pipeline configuration.

Cluster log

The Cluster module’s log.

Default file name: cluster.log

Configuration items: logfile and 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.

Default file name: -

Java module log

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

Default file name: java-module-name.log

Thread queue sizes log

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

Default file name: -

Persistence event log

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

Default file name: persistence.log

Configuration items: logfile and log-level in Persistence configuration

See also: