IdentifyChromeProcesses.py is a useful summary of an ETW trace, if you are a Chrome developer primarily interested in the mapping of process IDs to Chrome process types. However there is so much more than could be done, especially now that the Trace Processing library is available:
Obvious snippets that could be in a summary include:
Options used when recording the trace
The length (in time) of the trace
Whether there are any lost events or time inversions
Average CPU utilization (need to excluded rundown), and old sections of circular-buffer tracing, top CPU consumers, average disk utilization, active window/windows, whether CPU throttling was detected, QPC frequency, ???
What type of trace it is ("normal", heap tracing, heap snapshot)
If a heap tracing or heap snapshot trace then things like how many allocations, etc.
Ideally this summary would be in a delimited block so that the summary could be regenerated when new features are added, replacing the old summary. Maybe that would be best done by having it in a separate file, or injected into the trace, and then shown in a tooltip?
IdentifyChromeProcesses.py is a useful summary of an ETW trace, if you are a Chrome developer primarily interested in the mapping of process IDs to Chrome process types. However there is so much more than could be done, especially now that the Trace Processing library is available:
https://randomascii.wordpress.com/2020/01/05/bulk-etw-trace-analysis-in-c/
Obvious snippets that could be in a summary include:
Ideally this summary would be in a delimited block so that the summary could be regenerated when new features are added, replacing the old summary. Maybe that would be best done by having it in a separate file, or injected into the trace, and then shown in a tooltip?