MFT Tracing

MFT tracing can help to debug a variety of admin and transfer problems. Unless the problem is an SSH protocol issue, MFT tracing is typically sufficient to debug most issues. You can add tracing at the following levels:

Tracing Level	Description
System	The System Configuration page allows you to enable tracing for individual Internet Server or Command Center instances. This level of tracing produces a lot of trace data. Hence, only do this for short periods of time.
User	Tracing is enabled for all admin and transfer functions performed by this user. This is a good trace to enable when debugging admin problems.
Server	Tracing is enabled for all transfer functions and Command Center functions performed with this server. This is a good trace to enable when debugging transfer problems for a particular server. However, if a lot of data is transferred to this server, the traces can be pretty large and can affect transfer speed. Note that transfers to Platform Servers write a lot of data; all data sent to or received from the Platform Server is traced.
Transfer	Tracing is enabled for all transfer functions for this transfer definition. This is a good trace to enable when debugging transfer problems for a particular server when the problem typically happens for a single transfer definition.

MFT Traces are written to the logs or trace folder. Two types of trace files are typically written:

Types of Trace File	Example
User traces	user-trace-MFT-app-2020-12-18.txt
Transfer traces	IC1800001H-trace-cfjava-app.txt IC1800001H-trace-cfjava-comm.txt IC1800001H-trace-sshproxy-app.txt IC1800001H-trace-sshproxy-comm.txt

It is not a good idea to leave traces on for too long. The Diagnostics page shows you if traces are enabled. There are two places that show trace settings:

Trace Setting Places	Description
Active Trace Object Count	Shows how many trace objects are active.
Trace Settings	Shows details on the objects where tracing is enabled.