[GH-ISSUE #2892] H3 client stream errors lack detail #1080

New issue

Open

opened 2026-03-16 01:33:58 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 01:33:58 +03:00

Owner

Originally created by @marcus0x62 on GitHub (Mar 28, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2892

As reported in the discord channel, h3 client stream connection messages do not include the address of the remote nameserver, or which query is associated with a given failure. Log messages should include this information for troubleshooting purposes. The current error message:

WARN hickory_proto::h3::h3_client_stream: h3 connection failed: timeout

Originally created by @marcus0x62 on GitHub (Mar 28, 2025). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2892 As reported in the discord channel, h3 client stream connection messages do not include the address of the remote nameserver, or which query is associated with a given failure. Log messages should include this information for troubleshooting purposes. The current error message: ```WARN hickory_proto::h3::h3_client_stream: h3 connection failed: timeout```

kerem commented

2026-03-16 01:34:04 +03:00

Author

Owner

@djc commented on GitHub (Mar 29, 2025):

Ideally we'd use tracing's span support to make this better -- the span should record this context, and events within the span should lead to the log messages including data from the span.

@djc commented on GitHub (Mar 29, 2025): Ideally we'd use tracing's span support to make this better -- the span should record this context, and events within the span should lead to the log messages including data from the span.