[Agentless] Introduce global agentless configuration key

[dudikeleti]

Summary of changes

• Add DD_AGENTLESS_ENABLED as a configuration key.
• Generate ConfigurationKeys.AgentlessEnabled for all supported TFMs.

Reason for change

• Establish a global switch for consistent agentless configuration across supported products.
• Allow existing product-specific settings to remain compatibility fallbacks.

Implementation details

• Defaults agentless mode to disabled.
• Documents global-key precedence without changing product behavior in this PR.

[dd-trace-dotnet-ci-bot]

Execution-Time Benchmarks Report ⏱️

Execution-time results for samples comparing This PR (9059) and master.

⚠️ Potential regressions detected

HttpMessageHandler

Metric	Master (Mean ± 95% CI)	Current (Mean ± 95% CI)	Change	Status
.NET Framework 4.8 - Baseline
duration	190.35 ± (190.91 - 191.69) ms	214.63 ± (214.17 - 215.09) ms	+12.8%	❌⬆️
.NET Framework 4.8 - Bailout
duration	194.19 ± (194.09 - 194.56) ms	217.94 ± (217.80 - 218.63) ms	+12.2%	❌⬆️
.NET Framework 4.8 - CallTarget+Inlining+NGEN
duration	1151.33 ± (1150.44 - 1155.97) ms	1269.26 ± (1269.57 - 1276.80) ms	+10.2%	❌⬆️

📄 View the full report (charts + all metrics) →

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-15 15:56:36

Comparing candidate commit a40340d in PR branch dudik/agentless/introduce-global-agentless-key with baseline commit f1ae1d2 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 1 performance regressions! Performance is the same for 71 metrics, 0 unstable metrics, 65 known flaky benchmarks, 61 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:Benchmarks.Trace.DbCommandBenchmark.ExecuteNonQuery net472

• 🟥 throughput [-35702.251op/s; -32395.848op/s] or [-10.056%; -9.124%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472

• 🟥 throughput [-8744.483op/s; -8300.062op/s] or [-10.368%; -9.841%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild netcoreapp3.1

• 🟥 throughput [-9310.040op/s; -8119.835op/s] or [-9.466%; -8.256%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

• 🟥 allocated_mem [+1.555KB; +1.555KB] or [+47.240%; +47.254%]
• 🟥 execution_time [+310.034ms; +313.496ms] or [+153.850%; +155.568%]
• 🟥 throughput [-59.321op/s; -54.662op/s] or [-10.673%; -9.835%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

• 🟥 allocated_mem [+1.013KB; +1.013KB] or [+37.563%; +37.575%]
• unstable execution_time [+293.410ms; +354.147ms] or [+231.812%; +279.797%]
• 🟩 throughput [+63.441op/s; +67.750op/s] or [+8.364%; +8.933%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

• 🟥 allocated_mem [+1.088KB; +1.088KB] or [+40.343%; +40.355%]
• 🟥 execution_time [+394.461ms; +399.550ms] or [+349.083%; +353.586%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net472

• 🟥 allocated_mem [+4.693KB; +4.694KB] or [+98.806%; +98.821%]
• 🟥 throughput [-60664.258op/s; -60308.683op/s] or [-47.200%; -46.923%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody net6.0

• 🟥 allocated_mem [+3.816KB; +3.816KB] or [+80.699%; +80.711%]
• 🟩 execution_time [-16.224ms; -12.001ms] or [-7.577%; -5.605%]
• 🟥 throughput [-60147.077op/s; -57383.527op/s] or [-43.904%; -41.887%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleMoreComplexBody netcoreapp3.1

• 🟥 allocated_mem [+4.544KB; +4.544KB] or [+98.261%; +98.274%]
• 🟥 throughput [-48654.289op/s; -46410.650op/s] or [-43.989%; -41.961%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net472

• 🟥 allocated_mem [+1.315KB; +1.315KB] or [+106.388%; +106.404%]
• 🟥 throughput [-253776.165op/s; -250635.847op/s] or [-25.912%; -25.591%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody net6.0

• 🟥 allocated_mem [+479 bytes; +480 bytes] or [+39.212%; +39.221%]
• 🟩 execution_time [-26.826ms; -21.951ms] or [-11.963%; -9.789%]
• 🟥 throughput [-79602.220op/s; -55640.867op/s] or [-8.504%; -5.944%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1

• 🟥 allocated_mem [+1.280KB; +1.280KB] or [+105.947%; +105.963%]
• 🟥 throughput [-166544.847op/s; -150175.912op/s] or [-23.929%; -21.577%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net472

• 🟥 allocated_mem [+3.378KB; +3.378KB] or [+89.003%; +89.017%]
• 🟥 throughput [-72832.187op/s; -72068.871op/s] or [-49.015%; -48.502%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody net6.0

• 🟥 allocated_mem [+3.336KB; +3.336KB] or [+88.150%; +88.161%]
• 🟥 throughput [-73262.706op/s; -70378.270op/s] or [-46.616%; -44.781%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorMoreComplexBody netcoreapp3.1

• 🟥 allocated_mem [+3.264KB; +3.264KB] or [+88.493%; +88.506%]
• 🟥 throughput [-56143.571op/s; -53510.948op/s] or [-44.726%; -42.628%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net6.0

• 🟩 throughput [+307176.832op/s; +339010.959op/s] or [+10.243%; +11.304%]

scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1

• 🟩 execution_time [-19.187ms; -14.853ms] or [-8.845%; -6.847%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net472

• 🟩 allocated_mem [-13.759KB; -13.756KB] or [-42.324%; -42.316%]
• 🟥 execution_time [+300.542ms; +301.287ms] or [+150.170%; +150.543%]
• 🟩 throughput [+995.598op/s; +1014.406op/s] or [+10.996%; +11.204%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs net6.0

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• unstable execution_time [+298.629ms; +318.564ms] or [+150.599%; +160.653%]
• 🟩 throughput [+2054.896op/s; +2532.849op/s] or [+15.717%; +19.373%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs netcoreapp3.1

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• 🟥 execution_time [+300.537ms; +302.914ms] or [+151.387%; +152.585%]
• 🟩 throughput [+1765.497op/s; +1890.757op/s] or [+17.045%; +18.254%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net472

• 🟥 execution_time [+297.309ms; +298.852ms] or [+146.027%; +146.784%]
• 🟩 throughput [+517.004op/s; +537.180op/s] or [+13.706%; +14.241%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs net6.0

• 🟥 execution_time [+298.290ms; +300.625ms] or [+145.823%; +146.965%]
• 🟩 throughput [+2686.446op/s; +2746.223op/s] or [+39.029%; +39.897%]

scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1

• 🟥 execution_time [+299.525ms; +300.469ms] or [+149.702%; +150.174%]
• 🟩 throughput [+1342.947op/s; +1404.783op/s] or [+26.656%; +27.884%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net472

• 🟩 execution_time [-144.627µs; -140.681µs] or [-29.694%; -28.884%]
• 🟩 throughput [+838.054op/s; +863.818op/s] or [+40.817%; +42.072%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark net6.0

• 🟩 execution_time [-129.114µs; -100.577µs] or [-29.612%; -23.067%]
• 🟩 throughput [+749.482op/s; +894.718op/s] or [+32.584%; +38.899%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmark netcoreapp3.1

• 🟩 execution_time [-134.452µs; -111.872µs] or [-28.807%; -23.969%]
• 🟩 throughput [+700.380op/s; +792.953op/s] or [+32.331%; +36.604%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net472

• 🟩 execution_time [-125.963µs; -121.537µs] or [-34.009%; -32.814%]
• 🟩 throughput [+1329.960op/s; +1382.669op/s] or [+49.256%; +51.208%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack net6.0

• 🟩 execution_time [-96.501µs; -72.537µs] or [-30.808%; -23.157%]
• 🟩 throughput [+1062.384op/s; +1276.918op/s] or [+33.118%; +39.805%]

scenario:Benchmarks.Trace.Asm.AppSecWafBenchmark.RunWafRealisticBenchmarkWithAttack netcoreapp3.1

• 🟩 execution_time [-127.365µs; -100.527µs] or [-34.842%; -27.500%]
• 🟩 throughput [+1111.668op/s; +1327.646op/s] or [+39.893%; +47.644%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

• 🟥 execution_time [+299.799ms; +300.648ms] or [+149.630%; +150.054%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0

• 🟥 execution_time [+411.214ms; +419.886ms] or [+446.801%; +456.224%]
• 🟩 throughput [+763.295op/s; +978.006op/s] or [+6.272%; +8.036%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest netcoreapp3.1

• unstable execution_time [+300.659ms; +350.411ms] or [+228.288%; +266.064%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

• unstable execution_time [+259.495ms; +321.930ms] or [+119.313%; +148.020%]
• 🟥 throughput [-629.242op/s; -575.223op/s] or [-57.015%; -52.121%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0

• unstable execution_time [+198.043ms; +331.253ms] or [+84.398%; +141.166%]
• 🟥 throughput [-675.726op/s; -592.253op/s] or [-45.071%; -39.503%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1

• 🟥 execution_time [+343.199ms; +352.516ms] or [+205.273%; +210.845%]
• 🟥 throughput [-406.058op/s; -363.806op/s] or [-28.273%; -25.331%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net6.0

• 🟩 execution_time [-198.425µs; -144.730µs] or [-18.403%; -13.423%]
• 🟩 throughput [+155.873op/s; +218.577op/s] or [+16.807%; +23.567%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net6.0

• 🟩 execution_time [-161.219µs; -108.822µs] or [-8.167%; -5.513%]
• 🟩 throughput [+31.340op/s; +45.616op/s] or [+6.187%; +9.005%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

• 🟥 execution_time [+300.483ms; +302.935ms] or [+151.317%; +152.552%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net6.0

• 🟥 execution_time [+298.604ms; +303.467ms] or [+149.631%; +152.068%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch netcoreapp3.1

• 🟥 execution_time [+300.422ms; +304.063ms] or [+150.919%; +152.748%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

• 🟥 execution_time [+302.286ms; +303.874ms] or [+151.798%; +152.595%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net6.0

• 🟥 execution_time [+299.103ms; +303.067ms] or [+147.893%; +149.853%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync netcoreapp3.1

• 🟥 execution_time [+302.499ms; +306.941ms] or [+153.320%; +155.571%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

• 🟥 execution_time [+299.876ms; +301.916ms] or [+150.511%; +151.534%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net6.0

• 🟥 execution_time [+299.359ms; +308.660ms] or [+149.203%; +153.839%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync netcoreapp3.1

• 🟥 execution_time [+301.634ms; +304.961ms] or [+150.060%; +151.716%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net6.0

• 🟩 execution_time [-16.227ms; -12.545ms] or [-7.546%; -5.834%]
• 🟩 throughput [+21278.849op/s; +27875.453op/s] or [+5.837%; +7.647%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net472

• unstable execution_time [+35.144µs; +80.942µs] or [+8.681%; +19.993%]
• 🟥 throughput [-411.399op/s; -194.746op/s] or [-16.555%; -7.837%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark net6.0

• 🟩 allocated_mem [-20.248KB; -20.225KB] or [-7.386%; -7.378%]
• unstable execution_time [-26540.742ns; +28083.500ns] or [-5.246%; +5.551%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatAspectBenchmark netcoreapp3.1

• 🟩 allocated_mem [-16.332KB; -16.314KB] or [-5.954%; -5.947%]
• unstable execution_time [-74.335µs; -10.310µs] or [-12.882%; -1.787%]
• unstable throughput [+56.114op/s; +236.091op/s] or [+3.206%; +13.488%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net6.0

• 🟥 execution_time [+7.293µs; +11.405µs] or [+17.239%; +26.959%]
• 🟥 throughput [-5188.300op/s; -3367.987op/s] or [-21.841%; -14.178%]

scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark netcoreapp3.1

• unstable execution_time [-15.159µs; -7.467µs] or [-23.519%; -11.585%]
• unstable throughput [+1952.996op/s; +3611.116op/s] or [+11.982%; +22.155%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

• 🟥 execution_time [+301.573ms; +303.082ms] or [+152.432%; +153.194%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net6.0

• 🟥 execution_time [+302.476ms; +306.563ms] or [+153.959%; +156.040%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog netcoreapp3.1

• 🟥 execution_time [+297.682ms; +300.422ms] or [+149.027%; +150.399%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net6.0

• 🟩 throughput [+35775.611op/s; +41409.792op/s] or [+6.772%; +7.838%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

• 🟥 execution_time [+298.756ms; +301.205ms] or [+148.903%; +150.124%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net6.0

• 🟥 execution_time [+301.778ms; +304.271ms] or [+151.538%; +152.791%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog netcoreapp3.1

• 🟥 execution_time [+305.277ms; +307.994ms] or [+154.817%; +156.195%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

• 🟥 execution_time [+300.804ms; +301.600ms] or [+150.043%; +150.439%]
• 🟩 throughput [+60920059.249op/s; +61243393.941op/s] or [+44.366%; +44.601%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net6.0

• 🟥 execution_time [+423.209ms; +427.939ms] or [+526.336%; +532.219%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore netcoreapp3.1

• 🟥 execution_time [+298.624ms; +299.767ms] or [+148.947%; +149.517%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0

• 🟩 throughput [+108668.685op/s; +116438.102op/s] or [+10.146%; +10.871%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0

• 🟩 throughput [+90985.457op/s; +120429.816op/s] or [+7.042%; +9.321%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1

• 🟩 throughput [+71085.235op/s; +82162.165op/s] or [+7.060%; +8.160%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net6.0

• 🟩 throughput [+47236.933op/s; +52289.368op/s] or [+8.577%; +9.495%]

Known flaky benchmarks without significant changes:

• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_GetContext_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetAttributes_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_UpdateName_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_AddEvent_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_GetContext_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_RecordException_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetAttributes_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_SetStatus_Sampled netcoreapp3.1
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled net472
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled net6.0
• scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.TelemetrySpanBenchmark.StartSpan_UpdateName_Sampled netcoreapp3.1
• scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0
• scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool netcoreapp3.1
• scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OriginalCharSlice netcoreapp3.1
• scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net472
• scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog netcoreapp3.1
• scenario:Benchmarks.Trace.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
• scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472
• scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new global configuration key to enable “agentless” (direct-to-intake) behavior for supported products, with generated constants updated across target frameworks.

Changes:

• Added DD_AGENTLESS_ENABLED to the supported configuration catalog.
• Generated a new ConfigurationKeys.AgentlessEnabled constant for all supported TFMs.
• Documented precedence/behavior and default value (disabled).

Reviewed changes

Copilot reviewed 1 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tracer/src/Datadog.Trace/Generated/netstandard2.0/Datadog.Trace.SourceGenerators/ConfigurationKeysGenerator/ConfigurationKeys.g.cs	Adds generated constant and XML docs for DD_AGENTLESS_ENABLED.
tracer/src/Datadog.Trace/Generated/netcoreapp3.1/Datadog.Trace.SourceGenerators/ConfigurationKeysGenerator/ConfigurationKeys.g.cs	Adds generated constant and XML docs for DD_AGENTLESS_ENABLED.
tracer/src/Datadog.Trace/Generated/net6.0/Datadog.Trace.SourceGenerators/ConfigurationKeysGenerator/ConfigurationKeys.g.cs	Adds generated constant and XML docs for DD_AGENTLESS_ENABLED.
tracer/src/Datadog.Trace/Generated/net461/Datadog.Trace.SourceGenerators/ConfigurationKeysGenerator/ConfigurationKeys.g.cs	Adds generated constant and XML docs for DD_AGENTLESS_ENABLED.
tracer/src/Datadog.Trace/Configuration/supported-configurations.yaml	Registers DD_AGENTLESS_ENABLED with type/default and documentation for codegen and docs.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[andrewlock]

This is a Very general switch? 🤔 What products support this? I should think that we should want to get buy-in across all products even if they don't support agentless yet before introducing a switch like this 🤔

e.g. does this also impact CI Visibility? Does it do things like disable remote config (not available) and the discovery service? How will it interact with Feature flag agentless behaviours etc 😅

[dudikeleti]

Yes, there are a lot here 😅 This PR currently doesn't impact anything, so I didn't add an explanation, but I probably should have.

Eventually, we want a single switch for everything, with support for overrides, as well as Remote Config. We’ll discuss it.

For reference:
DataDog/libdatadog#2112
DataDog/dd-trace-py#19487
DataDog/dd-trace-py#19631

[bwoebi]

Yes, DD_AGENTLESS_ENABLED should support everything, but profiling (and the special FFE way of fetching via fastly) - for now.

I do however recommend to not provide a global agentless switch, until agentless RC is available. I.e. the experience is completely seamless across all languages, affecting all products equally.

Otherwise e.g. appsec won't work properly, neither DI etc.