Logging tools #1161
-
Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
The logging story for MsQuic is quite complex. We strive for extremely high performant logging (i.e. no/minimal overhead at gigabit transfer rates) so we cannot use qlog directly. Instead, on Windows we use manifested ETW and on Linux we use LTTng binary logging formats. Additionally, I created a very minimal ETW -> qlog convertor, but it's now woefully out of date. That being said, we do have significant tools of our own to analyze ETW traces (even in more detail in some aspects than qvis). We use Windows Performance Analyzer (WPA). All the necessary bits are currently going through the final approval stages to be shared externally to Microsoft (ETA this month). I will update this when I have more exact information. |
Beta Was this translation helpful? Give feedback.
The logging story for MsQuic is quite complex. We strive for extremely high performant logging (i.e. no/minimal overhead at gigabit transfer rates) so we cannot use qlog directly. Instead, on Windows we use manifested ETW and on Linux we use LTTng binary logging formats. Additionally, I created a very minimal ETW -> qlog convertor, but it's now woefully out of date.
That being said, we do have significant tools of our own to analyze ETW traces (even in more detail in some aspects than qvis). We use Windows Performance Analyzer (WPA). All the necessary bits are currently going through the final approval stages to be shared externally to Microsoft (ETA this month). I will update this when I…