[Native] Downgrade high-frequency ReJIT logs to debug - #9215
Conversation
918f590 to
f778d73
Compare
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. |
|
Maybe we can implement OTEL_LOG_LEVEL 🤔 |
BenchmarksBenchmark execution time: 2026-09-08 18:48:50 Comparing candidate commit f778d73 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 72 metrics, 0 unstable metrics, 66 known flaky benchmarks, 60 flaky benchmarks without significant changes.
|
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (9215) and master. ✅ No regressions detected |
Summary of changes
Changes two native log calls in
rejit_handler.cppfromLogger::InfotoLogger::Debug:"NGEN:: Processed with N inliners""Request ReJIT done for N methods"Reason for change
These are the two highest-frequency native info logs we've sampled, and they are written unconditionally (not gated on
DD_TRACE_DEBUG). Customers on Azure Functions accumulate gigabytes of native tracer logs in Kudu storage with debug logging off. See SLES-2871 for a concrete example: ~32K log files / ~20 GB filled a customer's disk and broke deploys, withDD_TRACE_DEBUGnot enabled. These two messages are the biggest single contributors to that volume.Implementation details
Two-line change; no API or config surface changes. In-repo precedent: #8618 downgraded similar high-frequency debugger-probe logs to debug.
Test coverage
It builds?
Other details
Out of scope (follow-ups if wanted): a general verbosity knob for the native logger (today it's a binary debug toggle fed solely from
DD_TRACE_DEBUG)