Skip to main content

Error and warning logging

The state of transformation packages is logged on several levels at the moment of transformation.

  1. The most general information such as start time, stop time, validity status and a short log may be previewed in the main processing log, e.g. in the Task Manager log (when transformation packages are launched this way).
  2. More detailed information which comes up at the moment of package operation is saved either to the Task Manager main log or to the log which is created separately while running packages using TransformationRunner.exe.

Logs include:

  1. the values of non-sensitive invocation parameters such as paths to files, a connection string without database passwords,
  2. worker thread start/stop,
  3. statistical information concerning performance,
  4. statistics of particular SQL command types duration (practically particular Access plans),
  5. statistics of a number of calls and time the processor spent in particular threads and blocks of a package,
  6. statistical information concerning validity,
  7. messages, levels and counters of particular types of errors caught,
  8. messages, levels and counters od particular types of warnings caught,
  9. counters of records passing through the blocks with counting capability (e.g. data classification, data profiler).

A detailed log also contains of every thousandth exception. It is aimed at preventing generating huge, unmanageable logs.

During operation, one of the logging levels may be set:

  1. None,
  2. Errors,
  3. Warnings,
  4. Info,
  5. Verbose.

image

While the TransformationRunner.exe,is running, it is possible to adjust values using keyboard shortcuts: Ctrl-T and Ctrl-t (increasing and decreasing the logging level, respectively). It can also be set with .NET TraceSwitch named "MasterTraceSwitch" in the configuration. Both runtime and plug-ins use the switch value. For example, a plug-in, which controls workflow processes, logs each request and control service response while duration at the Verbose level. It is very helpful while identifying problems during deployment. Among technical logs which concern particular stages of system operation, the following logs can be found: a system boot log, a task log, an end work log, and also the Task Hierarchy example logs with an invalid task.

See also​

Reading data from a database and writing it to a file

Creating a DOCX document by using a template

Integration with Active Directory