The translation log pane displays statistics and processing information that includes the following:
- FME version
- reader being used
- writer being used
- logging information
- warning messages
- command line, including published parameters
Information Messages
Information messages are displayed until the translation is complete. When the translation is complete, you can use the log window buttons to search for text, toggle word wrap, or edit log file settings in Tools > Options > Translation.
You can also right-click inside the log window and copy selected contents of the window directly to another application, or save the contents to a text file.
The log file is an important record of a translation and all the stages and processes within it. At first glance it might appear complex, even for a successful translation, but the information in here can be helpful when the output is not what was expected.
ERRORs
An ERROR in the log window signifies a problem that has caused FME to terminate processing. A typical example would be the inability to write the output dataset. It could just be that the user permissions are not correct, but since FME cannot create an output, there is no need to continue.
WARNings
A warning in the log window (displayed as WARN) signifies that there is a problem in the processing. The problem was not sufficient to cause FME to terminate the process, but you’ll want to check that the problem has not adversely affected your output. For example, features with an incompatible geometry for the destination Feature Type will not cause the process to fail, since FME can filter out these features. However the output will not be what was expected.
INFORMation
An information message (displayed as INFORM) is a non-error incident which signifies a piece of information that may help you determine whether your translation has been correctly processed. Typical information would be the number of features processed or confirmation of a particular setting for that dataset.
STATisticS
Statistics messages (displayed as STATS) provide information on the number of features read from the source and written to the destination datasets.
Note: The text in this area contains important information about the translation. If you ever get results that you did not expect in your output data, check the contents of the log.
Filtering Message Types
You can choose which information to display in the log through the Tools > FME Options > Translation menu. The options button 
on the right of the log window also displays the Translation options.
Log Timings
A useful option under Tools > FME Options > Translation is the ability to turn log timestamp information on or off:
Log timestamps indicate the absolute date and time for each step of the translation process. They also show the time taken by FME to process the previous stage and the cumulative time taken to reach that point in the translation.
You should keep Log timestamp information enabled. The messages might add to the amount of content in the window but they can be very useful when trying to analyze a translation.
Performance
In general, FME performance can be slowed by the contents of the log window scrolling past. This is especially true when there are many features that all trigger the same warning. Keep the log window closed or resized to a minimum when running a translation. You can open the window again for inspection after the translation is complete.
Interpreting the Messages
See Interpreting the Log for information on interpreting the contents of the log.
Note: Because some FME functionality is implemented using a third-party library (for example, GeoDatabase writing uses Esri ArcObjects), some information in the log window is reported directly from a product.
Saving Log Files by Default
You can choose to always save your log files:
- Select Tools > FME Options.
- Under Log Settings, check Save log to file. To add information to your log file instead of overwriting it each time you run the same translation, you can also check Append to log file.
Log files have the extension .log and by default
are saved in the same directory
as your workspace file.