Part of the process to enable CCI tracing is to specify the degree of information that will be traced, which can be done
by configuring the
ctf.cfg configuration file. The options are:
- mftrace.comp.mf.CCI.TCP#on=true|false
- If
true is specified then details of CCI API calls are logged to the trace file. The default value is
false, no tracing will be generated, even if the other options are set to true.
- #mftrace.comp.mf.CCI.TCP#protocol=true|false
- If
true is specified then details of protocol-level calls are logged to the trace file and the level of function tracing can be greatly
increased which might affect performance. The default value is
false.
- #mftrace.comp.mf.CCI.TCP#data=true|false
- If
true is specified then the contents of all buffers passed to and from the CCI functions are logged. The default value is
false.
CAUTION:
This type of tracing might expose sensitive data. Some applications might disable data tracing.
For example, to enable CCI API tracing and data tracing, but not protocol-level tracing, add the following:
mftrace.level.mf.cci=info
mftrace.comp.mf.CCI.TCP#on=true
mftrace.comp.mf.CCI.TCP#protocol=false
mftrace.comp.mf.CCI.TCP#data=true
The CCITRACE environment variable or the
CCI.INI file can also be used to control trace options.