Events (VSPerfCmd)
The VSPerfCmd.exe Events option controls Event Tracing for Windows (ETW) logging. ETW data is saved to an .etl file that is separate from the profiler data file. The data can be viewed in a report using the VSPerfReport /summary:etw command.
The Events option can be called at any time before the VSPerfCmd Shutdown command is called to stop profiling.
VSPerfCmd.exe /events {On|Off} {Guid|ProviderName} [,Flags[,Level]
Parameters
On|Off
Starts or stops collecting event data.Guid
The GUID of the provider control.ProviderName
The name of the provider that is registered with Windows Management Instrumentation (WMI).Flags
A "0x"-prefixed hexadecimal flags value that is defined by the event provider.Level
Specifies the amount of data collected. Level is defined by the event provider.
The Events option understands the following kernel keywords as provider names:
Process
Process eventsThread
Thread eventsImage
Image load and unload eventsDisk
Disk I/O eventsFile
File I/O eventsHardfault
Hard page faultsPagefault
Soft page faultsNetwork
Network eventsRegistry
Registry access events
Note that the Kernel Provider can only be enabled. It cannot be disabled, nor can its flags be modified, until the monitor shuts down.
Remarks
Note
When CLR ETW events are enabled, additional startup data is also collected in the Trace View report. To exclude startup events from appearing in the report, use the following command:
C:\<path>VSPerfCmd -events on, \".NET Common Language Runtime\", 0x7fffffff, 5
Important
If you do not exclude the startup events, then because these events are not listed in the Managed Object Format (MOF) file, they appear as GUIDs in the report. For more information, see this page on the Microsoft Web site: Sample Managed Object Format (MOF) File.
See Also
Reference
Concepts
Command-Line Profiling of Stand-Alone Applications