Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Decoded Logs Should Include Provider Name

Open
  • Is something wrong?
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

The issue names no files, tests, or entry points. Start by locating the code that formats decoded log events and trace how the provider identity is available. Done means decoded events include the provider name, matching the shown msquic example, without losing existing fields.

Written by the indexing model from the issue text.

Description

decode enhancement help wanted

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
Dominant language
C#
Stars
36
Forks
15
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/CLOG

All issues in microsoft/CLOG

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.