microsoft / microsoft/perfview
Verbosity Level Not Shown in the commandLine Property of the PerfView/CommandLineParameters
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.7k
- Forks
- 775
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 9
Description
This seems like a bug where despite adding the /ClrEventLevel:Verbose to collect a trace with all CLR Verbose events via perfview using a command such as:
PerfView start /AcceptEULA /NoGUI /Merge:true /zip:false /sessionName:e9a042b3-a75e-47f6-813f-afc5cf323f52 /GCCollectOnly /ClrEventLevel:Verbose /LogFile:C:\\V8\\heapcount_1\verbose.txt /DataFile:C:\\V8\\heapcount_1\verbose.etl
the PerfView/CommandLineParameters event doesn't mention this additional detail:
| Event Name | Time MSec | Process Name | commandLine | Rest |
| PerfView/CommandLineParameters | 1,735.222 | PerfView (27240) | "/DataFile:C:\V8\heapcount_1\verbose.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEvents:GC /NoGui /SessionName:fd0f4705-d616-4faa-bcdb-c0c196777e5f /LogFile:"C:\V8\heapcount_1\verbose.txt" /NoRundown /NoNGenRundown /Merge:True /GCCollectOnly | |
| PerfView/CommandLineParameters | 208,645.495 | PerfView (20216) | "/DataFile:C:\V8\heapcount_1\verbose.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEvents:GC /NoGui /SessionName:fd0f4705-d616-4faa-bcdb-c0c196777e5f /LogFile:"C:\V8\heapcount_1\verbose.txt" /NoRundown /NoNGenRundown /Merge:True /GCCollectOnly | |
| PerfView/CommandLineParameters | 214,751.470 | PerfView (20216) | "/DataFile:C:\V8\heapcount_1\verbose.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEvents:GC /NoGui /SessionName:fd0f4705-d616-4faa-bcdb-c0c196777e5f /LogFile:"C:\V8\heapcount_1\verbose.txt" /NoRundown /NoNGenRundown /Merge:True /GCCollectOnly |
The expected behavior is to be able to observe what verbosity level is being passed in for ClrEvents as the issue here is that the non-verbose commandline parameters are the same and thereby could be a point of confusion to those who rely on the event to decide what type of trace is captured.
Verbose CLR events not specified:
| Event Name | Time MSec | Process Name | commandLine | Rest |
| PerfView/CommandLineParameters | 531.885 | PerfView (19496) | "/DataFile:C:\\V8\\heapcount_1\gc.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEventLevel:Informational /ClrEvents:GC /NoGui /SessionName:161f9269-73bf-49b0-8f48-cb53204a15d2 /LogFile:"C:\\V8\\heapcount_1\gc.txt" /NoRundown /NoNGenRundown /Merge:True /Zip:False /GCCollectOnly | |
| PerfView/CommandLineParameters | 205,659.995 | PerfView (7856) | "/DataFile:C:\\V8\\heapcount_1\gc.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEventLevel:Informational /ClrEvents:GC /NoGui /SessionName:161f9269-73bf-49b0-8f48-cb53204a15d2 /LogFile:"C:\\V8\\heapcount_1\gc.txt" /NoRundown /NoNGenRundown /Merge:True /Zip:False /GCCollectOnly | |
| PerfView/CommandLineParameters | 210,603.619 | PerfView (7856) | "/DataFile:C:\\V8\\heapcount_1\gc.etl" /BufferSizeMB:256 /StackCompression /KernelEvents:Process /ClrEventLevel:Informational /ClrEvents:GC /NoGui /SessionName:161f9269-73bf-49b0-8f48-cb53204a15d2 /LogFile:"C:\\V8\\heapcount_1\gc.txt" /NoRundown /NoNGenRundown /Merge:True /Zip:False /GCCollectOnly |
CC: @Maoni0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PerfView start command and the PerfView/CommandLineParameters event described in the report, comparing traces with and without /ClrEventLevel:Verbose. Trace where the recorded command-line text is assembled and check any related tests. Done means the event distinguishes the requested CLR verbosity level while preserving existing command-line details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability, performance, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100