Production Logs

Whenever a Production script runs or a node within a script is tested, a log is generated. These internal Production logs are written and read using UTF8.

You can find the logs in the following default location:

<project name>/logs/production/<project path to script>/<script name>/YYYYMMDD_HHMMSS

This folder structure is created automatically when a Production job runs.

TIP: Production logs are best examined by using Show Results Mode.

Example Production Logs Explorer Structure

Production Logs in Explorer

You can modify the log location in Workbench using the Project Settings tab.

  1. Open the Project.

  2. Select Tools > Project Settings.

    The Project Settings tab opens to the Project Overview tab. If it is not open, select the Project Overview tab.

  3. Locate Log File Location below the Description box, and click the browse button.

  4. Navigate to the folder where you want to place the logs, or use the Add Folder button to create a folder.

  5. Click OK.

  6. Confirm that the new folder appears in Log File Location and in the Explorer pane on the left side of the page.

  7. Save the tab.

TIP: If in step 4 you manually enter a name for a nonexistent folder, rather than using Add Folder, and save the setting, the log folder structure is created the first time a script runs.

You can control how long log files are retained for each Production script.

  1. Open the Production script and click any white space in the Task Flow panel to ensure that no nodes are selected.

    The ClosedOverview panel displays below the task flow.

    Production Script Overview

  2. Locate the Logs Files section in the Overview panel, and click the Edit button.

    The ClosedEdit Log Settings dialog displays.

    Edit Log Settings dialog

  3. To specify that logs are deleted after X days, select Delete log files for this script after and enter the number of days.

  4. To change the default setting for the number of log files that are retained, ensure that Delete older log files when there are more than X log files is selected and enter the number of log files that you want to keep.

  5. Click OK.

    The log settings are saved for the script.

  6. TIP: If both check boxes in the setting dialog are checked, then logs are deleted if they meet either criteria (too old or too many).

If you set logging to debug, there is more verbose logging available. To turn debug logging on, add ShowDebug="True" to the top level 'CONF'"Production" object in di\solution\dl-dataroot\config\workbench.cfg

The attribute in Process nodes for handling the encoding of input files, External File Encoding, is also used for encoding the output, including the log files. This attribute allows you to override the default system encoding that is used when interpreting Integrator and Builder's output as captured in the logs. When blank, this attribute uses the default encoding—use the External File Encoding list to set an alternative encoding for the node. Setting the file encoding is recommended when using data with High Bit Latin-1 characters or Unicode characters.