-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Labels
decodeRelated to converting logs to textRelated to converting logs to textenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed
Description
Right now, here's an example of the decoded logs:
[0][][04:09:46.599830][strm][0x5623db187ea0] SF:16 FC:83705 QS:456734 MAX:36394 UNA:18169 NXT:36394 RECOV:0-0
[0][][04:09:46.599831][strm][0x5623db187ea0] unACKed: [18169, 36394]
[1][][04:09:46.599832][ udp][0x5623db0aede0] Recv 1252 bytes (segment=1252) Src=IPV4:16777343:48559 Dst=IPV4:16777343:32437
[0][][04:09:46.599833][67][84X][31] SH DestCid:"d9cf9e0323943186" KP:0 SB:0 (Payload 1227 bytes)
[1][][04:09:46.599833][conn][0x7fd550000b20] Queuing 1 UDP datagrams
[0][][04:09:46.599834][67][84X][31] STREAM ID:2 Offset:35179 Len:1215
[1][][04:09:46.599834][conn][0x7fd550000b20] Scheduling: 1
[0][][04:09:46.599848][wrkr][0x5623db0751f8] IsActive = 1, Arg = 1
Currently, only MsQuic logs are being collected, but eventually we might collect multiple providers/filters of logs in parallel. In order to better differentiate providers, we should include the name in the event, such as:
[1][][04:09:46.599833][msquic][conn][0x7fd550000b20] Queuing 1 UDP datagrams
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
decodeRelated to converting logs to textRelated to converting logs to textenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is needed