Events are written to the log file, trimming off the oldest events
to accommodate for the newer events when log file max is
Tracing stops when log file max is reached.
Multiple Sequential Logs (newfile):
Creates a new trace file when the max is reached for the original.
This is very useful for capturing an intermittent issue, without
fear of capturing an extremely large trace file. (This option is not available on Windows 2000)
Appends to existing log file. (This option is not available on Windows 2000)
TRACE DETAIL SETTINGS
This range can vary from 0x7 - 0xFFFFFF (0xFFFFFF recommended)
This range can vary from 1-16 (16 recommended)
TRACE FILE PATH
Set this to where you would like the resulting CDF trace file to be
stored. If this is not set, CDFControl creates the CDF trace
file (CDFLogFile.etl) in the same directory from where the
CDFControl.exe file is being run.
EVENT BUFFER MANAGEMENT
You have full control over the way CDFControl manages its
event buffers. Uncheck Use Default Settings to specify your
Size of each event buffer (buffer used to hold events when
capturing a trace), in KB
Minimum number of buffers to allocate for trace capture
Maximum number of buffers to allocate for trace capture
Flush Buffers Every:
Interval at which to flush buffers. Set to zero to use the default,
which is that buffers will be flushed when they are filled. Setting
it to a value greater than zero indicates the interval in seconds,
of which to flush the buffers.
An example of when this might be useful, is if events are taking a
longer time than expected to get displayed in a real-time trace.
The flush interval can then be increased to see if the buffers
needed to be flushed more quickly. For example, try flushing the
buffers every second, instead of waiting for them to become full,
or try manipulating the size and number of buffers.
REAL TIME VIEWING
Enable the Enable real-time viewing while capturing trace
check box for real-time viewing. For this to work correctly, you
need to ensure that a valid TMF search path is also set. With this
setting enabled, CDFControl will try to parse each trace
event being captured, in real-time using the TMF search path
provided. Events will still be written to the destination log file,
even though they are being viewed real-time.
Alternative to setting a TMF search path, you can choose to use
Dynamic TMF Download to obtain TMF's
(click to see more about dynamic TMF download).
A trace file path must also be set for real-time viewing to work
correctly, otherwise events/buffers will be lost.
STARTUP TRACE FILE PATH
Stores the location of where the startup CDF trace file will be
TRACE VIEWING SETTINGS
TMF SEARCH PATH
A semi-colon separated path to where the TMF files (to be used to
decrypt the trace events) are located. This can inlcude a UNC path
to a network share. This is required to be able to parse trace
FLUSH MEMORY CACHE AFTER CONSUMER SESSION
CDFControl can cache TMF format information read from TMF
files, so that subsequent parsing operations are faster. This
however, has a tradeoff of memory for performance. For example, if
this option is unchecked, parsing several small trace files (20MB
or less) can be much faster as format information will already be
cached in memory.
LOAD TRACE INTO VIEWER AFTER PARSED TO FILE
Enable this option to load a trace back into the viewer, after
being parsed to file. Select this option for maximum performance.
Especially useful for large trace files.