Example 8: Configuring Trace Buffers

The following command starts a trace log session and customizes the buffers for the session:

tracelog -start MyTrace -guid MyProvider.guid -f testtrace.etl -flag 2 -level ffff -b 128 -min 10 -max 30

The command starts a session named "MyTrace". It uses the -guid parameter to specify the provider file and the -f parameter to specify the name and location of the trace log.

It uses the -flag parameter to set the flag value to 2 and the -level parameter to set the level value to FFFF, which generates all available trace messages. These settings are specific to the provider.

To accommodate the high message rate, this command uses the -b parameter to increase the size of each buffer to 128 KB, the -min parameter to increase the minimum number of buffers to 10, and the -max parameter to increase the maximum number of buffers to 30.

In response, Tracelog starts a trace session and displays a few of the session properties. The properties that were set by the command are shown in bold type for easy identification.

Logger Started...
Enabling trace to logger 2
Operation Status:       0L      The operation completed successfully.

Logger Name:            MyTrace
Logger Id:              2
Logger Thread Id:       00000D7C
Buffer Size:            128 Kb
Maximum Buffers:        30
Minimum Buffers:        10
Number of Buffers:      10
Free Buffers:           9
Buffers Written:        1
Events Lost:            0
Log Buffers Lost:       0
Real Time Buffers Lost: 0
AgeLimit:               15
Log File Mode:          Sequential
Enabled tracing:        0x00000002
Log Filename:           d:\traces\testtrace.etl 

It is always important to watch the Events Lost counter in the trace session properties list. If you are losing events, rerun the trace session with increased buffer capacity (size, number, or both). To view the properties of a trace session, use tracelog -l or tracelog -qSessionName.



Send comments about this topic to Microsoft

© 2014 Microsoft