How to get win10 log

[zhanghenan-dev]

Hi,
I have got linux log with lttng(lttng-ust/ lttng-tools).
Now I want to get the log of Win10, but no response.
Here's how I did it, please help me to find which part is wrong:

1. quicetw.exe --local (Controller, Sleep(250) have changed to Sleep(2500000), always sleep)
2. start quicsample client, the other side ,there is a server (./quicsample -client -target:172.16.1.1 -unsecure)
3. quicetw.exe "C:\Windows\System32\LogFiles\WMI\quicetw.etl" --csv --trace --verbose (Consumer)

The result is no response, I think the correct operation after the third step should have print ?

[thhous-msft]

quicetw is not really the right tool for doing this. See the diagnostic page in the docs for how to grab logs.

https://github.com/microsoft/msquic/blob/main/docs/Diagnostics.md

You'll want to follow the netsh.exe portion for creating the raw etw log files.
https://github.com/microsoft/msquic/blob/main/docs/Diagnostics.md#netshexe

Then down in the windows section you'll see how to convert the logs. Since you're on windows 10, you'll need to follow the steps on how to install the manifest to be able to convert the logs.
https://github.com/microsoft/msquic/blob/main/docs/Diagnostics.md#windows-2

[zhanghenan-dev]

replies
I follow the Diagnostics.md, using the following command, convert the logs is abnormal.

1. netsh.exe trace start overwrite=yes report=dis correlation=dis traceFile=quic.etl provider={ff15e657-4f26-570e-88ab-0796b258d11c} level=0x5 keywords=0xffffffff
2. start msquic client
3. netsh.exe trace stop
4. netsh.exe trace convert quic.etl overwrite=yes

convert the logs:
[0]2328.0CB0::2022-04-28 14:37:45.019200800 [MSNT_SystemTrace]***
[0]2328.0CB0::2022-04-28 14:37:45.019200800 [MSNT_SystemTrace]***
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 33): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 34): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 34): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]0000.0000::2022-04-28 14:37:45.019200800 []Unknown( 35): GUID=9b79ee91-b5fd-41c0-a243-4248e266e9d0 (No Format Information found).
[0]1F48.1358::2022-04-28 14:38:11.830313700 []***
[0]1F48.1358::2022-04-28 14:38:11.831065400 []***
[0]1F48.1358::2022-04-28 14:38:11.831099500 []***
[0]1F48.1358::2022-04-28 14:38:11.831102100 []***
[0]1F48.1358::2022-04-28 14:38:11.831104400 []***
[0]1F48.1358::2022-04-28 14:38:11.832259700 []***
[0]1F48.1358::2022-04-28 14:38:11.832758000 []***
[0]1F48.1358::2022-04-28 14:38:11.832935000 []***
[0]1F48.1358::2022-04-28 14:38:11.832937300 []***
[0]1F48.1358::2022-04-28 14:38:11.832938900 []***
[0]1F48.1358::2022-04-28 14:38:11.832940600 []***
[0]1F48.1358::2022-04-28 14:38:11.832942200 []***
[0]1F48.1358::2022-04-28 14:38:11.832943800 []***

[zhanghenan-dev]

Use "wevtutil.exe" command to solve the problem, the log can be viewed, thank you