microsoft / microsoft/perfview
AutoLogger rolls ETL files in a format not accepted by PerfView
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.7k
- Forks
- 775
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 9
Description
AutoLogger can be configured to consume ETW events and publish the results in rolling ETL files with a given MaxFileSize
https://learn.microsoft.com/en-us/windows/win32/etw/configuring-and-starting-an-autologger-session
As the ETL files approach the file size limit, they are rolled in the following pattern:
- ProviderName.etl.001, ProviderName.etl.002, ProviderName.etl.003, etc.
The presence of the number after the .etl extension means that these files are not recognized by the PerfView application. The user has to manually rename the files to an accepted format. In addition, the library function GetMergeAllLogFiles does not recognize files under the AutoLogger format, which means that consumers of this library are presented with a FileNotFound exception when trying to process these log files programmatically.
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
Locate GetMergeAllLogFiles and the PerfView code that discovers ETL files; first compare their accepted filename patterns with AutoLogger's ProviderName.etl.001 format. Done when AutoLogger output can be consumed by PerfView and GetMergeAllLogFiles without manual renaming, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100