Documentation Center

Logging decisions

In the Content Porter logging configuration you specify whether to log or not, whether to use one log file and overwrite it with each export or import or to log to a separate file every time, where to log, the logging level, and whether to store the log file on the server or on the client.

Logging or no logging?

Your decision to log or not depends on your previous experience with Content Porter. If this is the first time you perform this specific transfer, switching logging on is strongly recommended. But if you are performing a regular transfer (especially one where, say, only some Components have changed), logging is not strictly necessary.

Overwrite old log files?

Overwriting your old log file means that old log information is lost. But creating a new log every time you perform an import or export can create a problem if your available disk space is limited. Generally, creating separate log files for each import or export (combined with a periodic manual cleanup) is recommended.

Where to log

Select a log location that has plenty of available space for your log.

Log level
The volume of your log depends on your log level. You can instruct Content Porter to log:
  • Only errors
  • Also warnings
  • All actions
Keep the log file on the server?

Select to keep the log file on the server if you expect to have enough room for the logs you create, and wish to keep them in a central location. If you need logs at the client's locations only, however, you can deselect this option.