feat(datadog): support forwarder_max_concurrent_requests#1811
Conversation
Binary Size Analysis (Agent Data Plane)Baseline: 6b23552 · Comparison: 7b60f6e · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
670542c to
7b60f6e
Compare
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (35)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
tobz
left a comment
There was a problem hiding this comment.
Looking at the forwarder worker logic in DDA, it looks like the concurrency limit is set per worker, so I think we'd actually want to set our concurrency limit to forwarder_num_workers * forwarder_max_concurrent_requests to properly mimic the behavior.
What changed
Implements
forwarder_max_concurrent_requestsas the ADP forwarder endpoint concurrency setting for #1363.forwarder_max_concurrent_requestsintoForwarderConfiguration::endpoint_concurrency().10.0to1at accessor read time..concurrency_limit(...)path and feeds it with the new setting.forwarder_num_workersfrom ADP runtime config usage and marks it unsupported in docs/registry.known-configs.jsonbookkeeping.Why
ADP previously used
forwarder_num_workersas the request concurrency setting, which did not match the Agent-facing config key for max concurrent outbound requests. This change makesforwarder_max_concurrent_requeststhe setting that controls ADP request concurrency.Validation
Existing tests