feat(feature-flags): add InitializeAsync to manual API with CallTarget instrumentation

[pavlokhrebto]

Summary of changes

Adds InitializeAsync to the Datadog.Trace.Manual feature flags API so that manual API users can trigger agentless delivery activation, just like OpenFeature users can.

This is PR 4 of a stacked PR series implementing agentless Feature Flags configuration delivery (FFL-2703), porting functionality from dd-trace-py#19331 and dd-trace-java#11892. Stacked on PR 1 #9040, PR 2 #9042, and PR 3 #9044.

Reason for change

.NET is the only SDK with a separate manual API (Datadog.Trace.Manual.FeatureFlagsSdk) that bypasses OpenFeature. With the new agentless default (PR 1), the agentless poller only starts at Activate(), which is called from InitializeAsync. The manual API had no InitializeAsync, so manual API users would be stuck with PROVIDER_NOT_READY forever unless they explicitly set remote_config.

Implementation details

• Datadog.Trace.Manual/FeatureFlags/FeatureFlagsSdk.cs — adds InitializeAsync(CancellationToken) stub marked [Instrumented] that returns Task.CompletedTask
• FeatureFlagsSdkInitializeAsyncIntegration.cs (new CallTarget) — intercepts the stub and calls TracerManager.Instance.FeatureFlags.InitializeAsync(cancellationToken), same pattern as the OpenFeature integration in PR 3
• supported_calltargets.g.json — registers the new calltarget targeting Datadog.Trace.Manual version 3.31.0–3.*.*
• InstrumentationDefinitions.g.cs (4 generated files) — auto-updated by the build to include the new integration in the allowlist

Test coverage

The InitializeAsync behavior is already tested in PR 3's FeatureFlagsModuleTests (activation, timeout, cancellation, no-delivery-start). This PR only adds the manual API stub and CallTarget wiring — no new tests needed since the underlying FeatureFlagsModule.InitializeAsync is unchanged.

Other details

Stacked PRs:

• PR 1 #9040: Configuration keys, settings, and endpoint derivation
• PR 2 #9042: UFC parser and agentless HTTP poller
• PR 3 #9044: Module wiring and OpenFeature activation
• PR 4 (this): Manual API activation

System tests: DataDog/system-tests#7496

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-28 14:31:28

Comparing candidate commit 433251c in PR branch pavlo.khrebto/EX-2703/ffe-manual-api with baseline commit 4a2cf7e in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 2 performance regressions! Performance is the same for 70 metrics, 0 unstable metrics, 69 known flaky benchmarks, 57 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 [-22577.786op/s; -18774.312op/s] or [-6.359%; -5.288%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync net472

• 🟥 throughput [-7104.835op/s; -5078.407op/s] or [-8.111%; -5.797%]

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.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan net472

• 🟥 throughput [-18337.169op/s; -10492.972op/s] or [-9.242%; -5.289%]

scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_AddEvent_Sampled net472

• 🟥 throughput [-19111.126op/s; -12275.963op/s] or [-10.913%; -7.010%]

scenario:Benchmarks.OpenTelemetry.InstrumentedApi.Trace.ActivityBenchmark.StartSpan_SetStatus_Sampled net472

• 🟥 throughput [-27516.537op/s; -21841.056op/s] or [-14.006%; -11.117%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472

• 🟥 throughput [-10860.219op/s; -10319.663op/s] or [-12.877%; -12.236%]

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

• 🟥 throughput [-10098.629op/s; -8450.263op/s] or [-10.268%; -8.592%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

• 🟥 allocated_mem [+1.573KB; +1.573KB] or [+47.789%; +47.804%]
• 🟥 execution_time [+312.064ms; +316.718ms] or [+154.857%; +157.167%]
• 🟥 throughput [-69.675op/s; -61.790op/s] or [-12.536%; -11.117%]

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

• 🟥 allocated_mem [+1.013KB; +1.013KB] or [+37.563%; +37.575%]
• 🟥 execution_time [+379.362ms; +380.801ms] or [+299.719%; +300.856%]
• 🟩 throughput [+61.444op/s; +63.827op/s] or [+8.101%; +8.415%]

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

• 🟥 allocated_mem [+1.088KB; +1.088KB] or [+40.343%; +40.355%]
• 🟥 execution_time [+398.091ms; +400.549ms] or [+352.296%; +354.471%]

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

• 🟥 allocated_mem [+4.725KB; +4.725KB] or [+99.465%; +99.482%]
• 🟥 throughput [-59688.708op/s; -59276.280op/s] or [-46.441%; -46.120%]

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

• 🟥 allocated_mem [+3.848KB; +3.848KB] or [+81.379%; +81.391%]
• 🟩 execution_time [-16.389ms; -12.220ms] or [-7.654%; -5.707%]
• 🟥 throughput [-59915.627op/s; -57160.596op/s] or [-43.735%; -41.724%]

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

• 🟥 allocated_mem [+4.576KB; +4.576KB] or [+98.954%; +98.966%]
• 🟥 throughput [-48722.401op/s; -46463.193op/s] or [-44.051%; -42.008%]

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

• 🟥 allocated_mem [+1.348KB; +1.348KB] or [+109.063%; +109.078%]
• 🟥 throughput [-283608.062op/s; -279048.595op/s] or [-28.958%; -28.492%]

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

• 🟥 allocated_mem [+511 bytes; +512 bytes] or [+41.822%; +41.834%]
• 🟩 execution_time [-26.079ms; -21.234ms] or [-11.630%; -9.469%]
• 🟥 throughput [-112405.316op/s; -89289.308op/s] or [-12.008%; -9.539%]

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

• 🟥 allocated_mem [+1.312KB; +1.312KB] or [+108.600%; +108.616%]
• 🟥 throughput [-161972.877op/s; -146145.617op/s] or [-23.272%; -20.998%]

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

• 🟥 allocated_mem [+3.378KB; +3.378KB] or [+89.003%; +89.017%]
• 🟥 throughput [-72695.922op/s; -71886.899op/s] or [-48.924%; -48.379%]

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

• 🟥 allocated_mem [+3.336KB; +3.336KB] or [+88.150%; +88.161%]
• 🟥 throughput [-72719.376op/s; -69827.889op/s] or [-46.270%; -44.430%]

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

• 🟥 allocated_mem [+3.264KB; +3.264KB] or [+88.493%; +88.506%]
• 🟥 throughput [-56316.009op/s; -53624.681op/s] or [-44.863%; -42.719%]

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

• 🟩 throughput [+334459.673op/s; +376862.170op/s] or [+11.152%; +12.566%]

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

• 🟩 execution_time [-19.102ms; -14.766ms] or [-8.805%; -6.807%]

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

• 🟩 allocated_mem [-13.759KB; -13.757KB] or [-42.326%; -42.318%]
• 🟥 execution_time [+299.698ms; +300.539ms] or [+149.749%; +150.169%]
• 🟩 throughput [+988.389op/s; +1040.654op/s] or [+10.917%; +11.494%]

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

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• 🟥 execution_time [+299.321ms; +302.405ms] or [+150.948%; +152.503%]
• 🟩 throughput [+2488.170op/s; +2698.997op/s] or [+19.031%; +20.643%]

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

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• 🟥 execution_time [+298.990ms; +316.323ms] or [+150.608%; +159.339%]
• 🟩 throughput [+1517.975op/s; +1857.711op/s] or [+14.655%; +17.935%]

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

• 🟥 execution_time [+296.215ms; +297.418ms] or [+145.489%; +146.080%]
• 🟩 throughput [+577.488op/s; +587.863op/s] or [+15.309%; +15.584%]

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

• 🟥 execution_time [+293.449ms; +296.907ms] or [+143.456%; +145.147%]
• 🟩 throughput [+2552.307op/s; +2636.925op/s] or [+37.080%; +38.310%]

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

• 🟥 execution_time [+300.756ms; +301.910ms] or [+150.318%; +150.894%]
• 🟩 throughput [+1396.947op/s; +1418.731op/s] or [+27.728%; +28.161%]

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

• 🟩 execution_time [-146.226µs; -142.246µs] or [-30.022%; -29.205%]
• 🟩 throughput [+851.183op/s; +877.548op/s] or [+41.456%; +42.741%]

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

• 🟩 execution_time [-138.859µs; -112.156µs] or [-31.847%; -25.723%]
• 🟩 throughput [+859.790op/s; +982.934op/s] or [+37.380%; +42.734%]

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

• 🟩 execution_time [-142.494µs; -120.466µs] or [-30.530%; -25.810%]
• 🟩 throughput [+775.310op/s; +858.788op/s] or [+35.790%; +39.643%]

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

• 🟩 execution_time [-128.463µs; -124.021µs] or [-34.684%; -33.485%]
• 🟩 throughput [+1370.964op/s; +1424.586op/s] or [+50.774%; +52.760%]

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

• 🟩 execution_time [-100.619µs; -76.908µs] or [-32.122%; -24.553%]
• 🟩 throughput [+1146.261op/s; +1352.863op/s] or [+35.732%; +42.173%]

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

• 🟩 execution_time [-137.350µs; -114.950µs] or [-37.573%; -31.446%]
• 🟩 throughput [+1322.736op/s; +1460.202op/s] or [+47.468%; +52.401%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

• 🟥 execution_time [+299.692ms; +300.698ms] or [+149.577%; +150.079%]

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

• unstable execution_time [+321.044ms; +393.973ms] or [+348.828%; +428.068%]
• 🟩 throughput [+929.780op/s; +1127.538op/s] or [+7.640%; +9.265%]

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

• 🟥 execution_time [+367.236ms; +370.569ms] or [+278.839%; +281.370%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

• unstable execution_time [+306.155ms; +368.424ms] or [+140.767%; +169.398%]
• 🟥 throughput [-564.260op/s; -516.701op/s] or [-51.127%; -46.818%]

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

• unstable execution_time [+144.726ms; +290.919ms] or [+61.676%; +123.978%]
• 🟥 throughput [-670.567op/s; -587.112op/s] or [-44.727%; -39.161%]

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

• 🟥 execution_time [+325.047ms; +336.673ms] or [+194.416%; +201.370%]
• 🟥 throughput [-387.147op/s; -349.712op/s] or [-26.957%; -24.350%]

scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice netcoreapp3.1

• unstable throughput [+18.704op/s; +59.670op/s] or [+5.376%; +17.152%]

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

• 🟩 execution_time [-156.685µs; -130.684µs] or [-7.937%; -6.620%]
• 🟩 throughput [+36.217op/s; +44.011op/s] or [+7.150%; +8.688%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

• 🟥 execution_time [+303.538ms; +305.336ms] or [+152.856%; +153.761%]

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

• 🟥 execution_time [+299.271ms; +309.842ms] or [+149.965%; +155.262%]

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

• 🟥 execution_time [+302.897ms; +306.497ms] or [+152.162%; +153.971%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

• 🟥 execution_time [+301.005ms; +303.435ms] or [+151.155%; +152.375%]

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

• 🟥 execution_time [+297.631ms; +316.027ms] or [+147.165%; +156.261%]

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

• 🟥 execution_time [+301.469ms; +305.785ms] or [+152.798%; +154.985%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

• 🟥 execution_time [+299.569ms; +301.301ms] or [+150.356%; +151.226%]

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

• unstable execution_time [+297.292ms; +320.075ms] or [+148.173%; +159.528%]
• 🟩 throughput [+30590.417op/s; +51073.877op/s] or [+6.074%; +10.142%]

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

• 🟥 execution_time [+300.974ms; +304.126ms] or [+149.732%; +151.300%]

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

• 🟩 execution_time [-17.318ms; -13.642ms] or [-8.053%; -6.344%]

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

• 🟩 throughput [+15083.378op/s; +20785.727op/s] or [+5.506%; +7.587%]

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

• unstable execution_time [+13.881µs; +62.070µs] or [+3.429%; +15.332%]

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

• 🟩 allocated_mem [-19.607KB; -19.583KB] or [-7.152%; -7.143%]
• unstable execution_time [-17.631µs; +40.646µs] or [-3.485%; +8.033%]

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

• unstable execution_time [-53.398µs; +6.821µs] or [-9.254%; +1.182%]

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

• unstable execution_time [+9.048µs; +13.994µs] or [+21.387%; +33.079%]
• 🟥 throughput [-5921.057op/s; -4018.762op/s] or [-24.926%; -16.918%]

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

• unstable execution_time [-15.606µs; -7.780µs] or [-24.212%; -12.071%]
• unstable throughput [+2102.986op/s; +3792.153op/s] or [+12.903%; +23.266%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

• 🟥 execution_time [+301.590ms; +303.041ms] or [+152.440%; +153.174%]

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

• 🟥 execution_time [+302.032ms; +304.560ms] or [+153.733%; +155.020%]

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

• 🟥 execution_time [+300.560ms; +302.766ms] or [+150.467%; +151.572%]

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

• 🟩 throughput [+32554.304op/s; +36619.981op/s] or [+6.162%; +6.931%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

• 🟥 execution_time [+298.931ms; +301.034ms] or [+148.990%; +150.038%]

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

• 🟥 execution_time [+300.787ms; +302.864ms] or [+151.041%; +152.084%]

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

• 🟥 execution_time [+303.256ms; +305.491ms] or [+153.792%; +154.925%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

• 🟥 execution_time [+300.052ms; +301.018ms] or [+149.668%; +150.149%]
• 🟩 throughput [+61189118.831op/s; +61522199.110op/s] or [+44.562%; +44.804%]

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

• unstable execution_time [+347.852ms; +404.071ms] or [+432.616%; +502.534%]

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

• 🟥 execution_time [+299.802ms; +300.910ms] or [+149.534%; +150.087%]

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

• 🟩 throughput [+98242.995op/s; +107014.951op/s] or [+9.173%; +9.992%]

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

• 🟩 throughput [+59469.082op/s; +67632.124op/s] or [+5.906%; +6.717%]

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

• 🟩 throughput [+49487.697op/s; +55376.584op/s] or [+8.986%; +10.055%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0

• 🟩 throughput [+62475.667op/s; +81876.121op/s] or [+6.980%; +9.148%]

Known flaky benchmarks without significant changes:

• 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 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 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.OptimizedCharSliceWithPool net472
• scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSliceWithPool net6.0
• 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.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.StartFinishSpan net6.0
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
• scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472
• scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

[dd-trace-dotnet-ci-bot]

Execution-Time Benchmarks Report ⏱️

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

✅ No regressions detected

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

[Copilot]

Pull request overview

Adds a new InitializeAsync(CancellationToken) entry point to the Datadog.Trace.Manual Feature Flags manual API so manual users can explicitly trigger Feature Flags configuration delivery activation (agentless or Remote Configuration) via CallTarget instrumentation, aligning behavior with the OpenFeature path introduced earlier in the stacked series.

Changes:

• Added FeatureFlagsSdk.InitializeAsync(CancellationToken) stub to Datadog.Trace.Manual, marked [Instrumented], to act as the interception point.
• Added a new CallTarget integration that intercepts the stub and delegates to TracerManager.Instance.FeatureFlags.InitializeAsync(cancellationToken).
• Registered the new CallTarget in the supported calltargets manifest and updated generated allowlists/definitions accordingly.

Reviewed changes

Copilot reviewed 3 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tracer/src/Datadog.Tracer.Native/Generated/generated_calltargets.g.cpp	Adds the native generated calltarget entry for Datadog.Trace.Manual FeatureFlagsSdk.InitializeAsync.
tracer/src/Datadog.Trace/Generated/netstandard2.0/Datadog.Trace.SourceGenerators/InstrumentationDefinitionsGenerator/InstrumentationDefinitions.g.cs	Updates generated instrumentation allowlist to include the new integration type.
tracer/src/Datadog.Trace/Generated/netcoreapp3.1/Datadog.Trace.SourceGenerators/InstrumentationDefinitionsGenerator/InstrumentationDefinitions.g.cs	Updates generated instrumentation allowlist to include the new integration type.
tracer/src/Datadog.Trace/Generated/net6.0/Datadog.Trace.SourceGenerators/InstrumentationDefinitionsGenerator/InstrumentationDefinitions.g.cs	Updates generated instrumentation allowlist to include the new integration type.
tracer/src/Datadog.Trace/Generated/net461/Datadog.Trace.SourceGenerators/InstrumentationDefinitionsGenerator/InstrumentationDefinitions.g.cs	Updates generated instrumentation allowlist to include the new integration type.
tracer/src/Datadog.Trace/ClrProfiler/AutoInstrumentation/ManualInstrumentation/FeatureFlags/FeatureFlagsSdkInitializeAsyncIntegration.cs	New CallTarget integration: replaces the stub’s return task with the tracer’s FeatureFlagsModule.InitializeAsync(...).
tracer/src/Datadog.Trace.Manual/FeatureFlags/FeatureFlagsSdk.cs	Adds the public manual API stub InitializeAsync(CancellationToken) returning Task.CompletedTask for instrumentation to intercept.
tracer/build/supported_calltargets.g.json	Registers the new manual API InitializeAsync calltarget for versions 3.31.0–3.*.*.

---

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

[pavlokhrebto]

The failing system_tests job is inherited from #9044 and is expected until DataDog/system-tests#7612 merges.

test_default_capability_completeness rejects capability 46 (FFE_FLAG_CONFIGURATION_RULES) because capabilities.yml has no dotnet entry for it yet. #7612 adds one at '>=3.53.0'. Details in #9044 (comment).