Conversation
…integration/DnsClient/20260928-131019
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (9355) and master.
|
|||||||||||||||
| Metric | Master (Mean ± 95% CI) | Current (Mean ± 95% CI) | Change | Status |
|---|---|---|---|---|
| .NET Framework 4.8 - Bailout | ||||
| duration | 76.74 ± (76.57 - 76.91) ms | 82.53 ± (82.08 - 82.97) ms | +7.5% | ❌⬆️ |
BenchmarksBenchmark execution time: 2026-10-02 13:01:15 Comparing candidate commit 9f36bdb in PR branch Found 0 performance improvements and 11 performance regressions! Performance is the same for 61 metrics, 0 unstable metrics, 74 known flaky benchmarks, 49 flaky benchmarks without significant changes.
|
Summary of changes
Add an instrumentation for DNS Client, creating spans for queries
Also added a sample app that includes a "fake DNS" (no external dependency && no docker dependency)
And tests with snapshots
Reason for change
On the one hand, to battle test the instrumentation generation toolkit,
But also DnsClient.NET is present on 729,786 customer hosts in our package catalog, ranking 42nd among non-System/non-Microsoft .NET packages—just ahead of RabbitMQ.Client at 702,156 hosts. Its broad adoption is also reflected by nearly 500 million downloads on NuGet. This integration brings .NET in line with the DNS visibility already offered by Datadog’s Node.js and Go tracers.
I don't have an explicit demand from a customer to show though.
Implementation details
generated using the #apm-integrations-ai-toolkit
I did a manual pass afterwards to:
Test coverage
Other details
Known blind spot: cache hits vs actual queries are not distinguished.