Table of contents
Collapse the table of content
Expand the table of content

Example 13: Creating a Global Logger Session

Last Updated: 11/22/2016

A Global Logger trace session differs from other trace sessions in that it reads its configuration parameters from registry entries. Because Tracelog handles these differences for you, the commands that you use to start and stop Global Logger trace sessions do not differ much from those for other sessions. However, you cannot update a Global Logger session and, after stopping the session, you must use a tracelog -remove command to reset the registry entries created for the session.

Also, the tracelog -start command does not start the trace session; it just creates and configures it. The session starts when you reboot the system.

The following command is the simplest command that configures a Global Logger session. It uses the tracelog -start command with the reserved GlobalLogger name. Tracelog uses the default values for all other parameters.

tracelog -start GlobalLogger

In response, Tracelog creates a GlobalLogger subkey in HKLM\SYSTEM\CurrentControlSet\Control\WMI with a registry entry for each parameter. It creates a Start entry in the subkey and sets its value to `1.

Because the command did not include the -f parameter, the trace log for this session is stored in the default location for Global Logger trace sessions, %SystemRoot%\System32\LogFiles\WMI\trace.log. To view the log, use Tracefmt or TraceView with the System.tmftrace message format file.

After the session is configured, reboot the system to start the trace session.

The following command stops the trace session, but it does not affect the registry entries.

tracelog -stop GlobalLogger

Then, to reset the registry entries, use the following command.

tracelog -remove GlobalLogger

This command deletes any registry entries for optional parameters (none, in this case). It leaves the GlobalLogger subkey and the Start entry, but it sets the value of Start to 0 (do not start).

The tracelog -remove command is not required. You can leave the entries in the registry and use them the next time you run a Global Logger trace session. If you start the session with different parameters, Tracelog replaces the values of the registry entries with the values specified in the tracelog -start command.

Send comments about this topic to Microsoft

© 2017 Microsoft