When you enable tracing from the Site Settings window, Insight creates a current trace file for each Insight process created when the related Integration Process (IP) runs. The Insight IP configuration determines how the contents of the current trace file are saved in an archive trace file.
You can enable tracing in Workbench and the Console, but you can only specify the location of the trace folder in the Workbench.
A current trace file is created for:
A current trace file is generated for an Insight process and for Insight message processors:
[Scribe_proc].log, where [Scribe_proc] is the Insight process that generated the trace file. For example, when Workbench runs, a current trace file, TWorkbench.log, is created.MessageProcessor[ProcGroup]_[XX].log, where [ProcGroup] is the name of the processor group assigned to an IP, and [XX] is the ID that is assigned to the message processor after it is initialized. This ID can be 00, 01, 02, ... 0N, where N is the highest number of message processor licensed and running. The Trace_Proc_00.log file is used to record file-based, time-based, and query-based IP messages. All other message processor trace files are used to record queue-based IP messages. Note: If message processor trace information is generated before an ID is assigned, the current trace file, [GUID].log, is created, where [GUID] is the Microsoft GUID that is associated with the message processor before a process ID is assigned. Review this log file for critical information that may affect the message processor functionality.
Archive tracing files are saved in the C:\Users\Public\Public Documents\Scribe\Tracing folder. Before editing an archive tracing file, stop the process associated with the file. Then, after you have edited the file, restart the associated process.
| Note: |
You may require administrator rights to edit an archive tracing file. |
In the configuration file for each Insight process for which tracing can be enabled, you can specify when the current trace file is archived. The contents of the current trace file are archived when the first of the following configured settings is triggered:
By default, archive trace files are created in the *\Public\Public Documents\Scribe\Tracing folder. You can change this folder on the Tracing tab in the Application Settings dialog box of the Workbench.
Archive trace files are named:
[Scribe_proc].[Date].[Number].log
where:
Make logging changes in the loggingConfigurations section of the configuration file for the process, in the \Program Files (x86)\Scribe folder.
If an Insight process has tracing enabled and is configured to archive at midnight, but the size of the current trace file does not exceed the configured archive size, the contents are archived to an archive trace file when the IP is run on a subsequent calendar day.
For example, if a DTS is run in Workbench on January 1, 2014, but that run does not generate enough data to trigger writing the contents of TWorkbench.log to an archive trace file, the trace information remains in TWorkbench.log until a DTS is next run in Workbench. If the next DTS is runs on January 6, 2014, the trace information in TWorkbench.log from January 1 is written to the archive trace file, TWorkbench.2014-01-06.1.log. Then, new trace information from the January 6 run is written to TWorkbench.log. When the size of TWorkbench.log triggers creating an archive trace file on January 6, Workbench writes the trace information to TWorkbench.2014-01-6.2.log, and so on.
You can turn tracing on or off from the Console. On the Tracing tab in the Site Settings window, click:
This button is only enabled if the path to a Tracing folder is specified in Workbench.
Whenever you change the tracing settings in the Console, you must restart Scribe services.
See also