Skip to content

[Feature Flags] Add agentless EVP fallback transport - #9235

Draft
leoromanovsky wants to merge 4 commits into
masterfrom
leo.romanovsky/fflsdk-189-evp-fallback-dotnet-master
Draft

[Feature Flags] Add agentless EVP fallback transport#9235
leoromanovsky wants to merge 4 commits into
masterfrom
leo.romanovsky/fflsdk-189-evp-fallback-dotnet-master

Conversation

@leoromanovsky

@leoromanovsky leoromanovsky commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Reason for change / Motivation

We are shipping an Agentless, CDN-delivered Feature Flags configuration mode to simplify customer deployments. The core telemetry produced by the SDK still needs a safe network path off the process: prefer an available Agent or serverless proxy, then fall back to Datadog's direct EVP intake when Agentless credentials are available.

Without this change, .NET can receive Agentless configuration but exposure events still use the historical Agent-only EVP client and are lost when no Agent or serverless-init is present. This implements the .NET transport portion of FFLSDK-189.

Summary of changes / Changes

  • Adds one Feature Flags EVP route state machine shared by exposure delivery and the future flag-evaluation writer.
  • Selects an advertised local EVP v4 route before v2, but only when /info confirms that the Agent forwards both DD-EVP-ORIGIN identity headers.
  • Falls back only in Agentless mode to the canonical direct HTTPS paths, with the API key restricted to direct intake and the EVP subdomain header restricted to the local relay.
  • Sends exact logical producer identity (dd-trace-dotnet and the tracer version) on both routes.
  • Shares strict DD_SITE normalization between Agentless configuration and direct event delivery and disables automatic redirects for credential-bearing direct requests.
  • Keeps direct routing sticky, bounds unavailable-route recovery, and limits same-batch replay to local 404/405 or definitive pre-send failures. Ambiguous failures and 403/429/5xx responses are never replayed; future batches switch to direct when credentials exist, otherwise the route enters bounded unavailable recovery.
  • Flushes queued exposures during shutdown with a bounded wait and blocks post-dispose enqueue races.

Implementation details / Decisions

  • Remote Config deliberately retains its historical fixed EVP v2 client. It does not subscribe to discovery, acquire direct credentials, or enter the Agentless cooldown state.
  • Agentless local selection consumes the tracer's shared discovery stream instead of creating a second /info loop. Recovery after a failed route permits one concurrent post-cooldown route probe; a discovery callback can restore the route sooner.
  • Direct intake is terminal for the process lifetime. A direct failure never loops back to the Agent.
  • This PR wires exposures. It exposes the same compressed send path and route state for the flag-evaluation work tracked in #9139, but does not absorb that payload, aggregation, or privacy work.
  • The small backwards-compatible redirect opt-out in the generic HTTP factories is sufficient for this direct sender. The broader API-key redirect guard in #9064 can subsume that hook later; this PR does not depend on it.
  • The branch contains signed commits directly on master and has no unmerged PR ancestry.
  • Provider-lifecycle foundation #9044 merged on September 14 and is now included through master. The conflict resolution preserves its lazy exposure creation, deferred/idempotent activation and cleanup while injecting shared discovery into the EVP transport.

Test coverage / Validation

Merged master 773007d736d6eda017b333b9d61aa5ebef6fb73f; exact candidate 7eba07853048a9d2e61f506051dca6984287c3e1.

  • dotnet test tracer/test/Datadog.Trace.Tests/Datadog.Trace.Tests.csproj -f net10.0 --filter 'FullyQualifiedName~FeatureFlags|FullyQualifiedName~Agent.DiscoveryServiceTests' --verbosity minimal — 658 passed, 0 failed, 0 skipped.
  • dotnet format whitespace tracer/test/Datadog.Trace.Tests/Datadog.Trace.Tests.csproj --no-restore --verify-no-changes --include tracer/src/Datadog.Trace/FeatureFlags/FeatureFlagsModule.cs tracer/src/Datadog.Trace/TracerManagerFactory.cs tracer/test/Datadog.Trace.Tests/FeatureFlags/FeatureFlagsModuleTests.cs --verbosity minimal — passed.
  • git diff --check — passed. The new merge commit is GitHub verified: verified=true, reason=valid.
  • Added a production-factory regression proving shared discovery, no Remote Config subscription in Agentless mode, deferred/idempotent source activation, and subscription/source disposal.
  • Existing transport tests cover local/direct paths and headers, credential isolation, redirects, site validation, v4/v2 preference and capabilities, no-replay cases, shared discovery, sticky direct, bounded recovery and shutdown.

End-to-end gate

Earlier exact-artifact runs failed before transport was exercised: the old candidate did not start Agentless UFC polling because #9044 was missing. That foundation is now merged; the former external blocker is resolved.

Neither direct nor serverless-init system tests have been rerun on this combined candidate. Rebuild this exact SHA and validate both routes next; passing unit tests is not backend-intake proof. Broader framework builds and current CI are not claimed from older heads.

No system-tests or dogfooding files are changed by this PR.

@linear-code

linear-code Bot commented Sep 12, 2026

Copy link
Copy Markdown

FFLSDK-189

@leoromanovsky leoromanovsky mentioned this pull request Sep 12, 2026
Draft
3 tasks
@pr-commenter

pr-commenter Bot commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-09-19 04:08:56

Comparing candidate commit 7eba078 in PR branch leo.romanovsky/fflsdk-189-evp-fallback-dotnet-master with baseline commit 773007d in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 11 performance regressions! Performance is the same for 61 metrics, 0 unstable metrics, 72 known flaky benchmarks, 54 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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+9.290%; +9.300%]
  • 🟥 throughput [-35773.513op/s; -33046.590op/s] or [-10.076%; -9.308%]

scenario:Benchmarks.Trace.DbCommandBenchmark.ExecuteNonQuery net6.0

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+8.939%; +8.950%]

scenario:Benchmarks.Trace.DbCommandBenchmark.ExecuteNonQuery netcoreapp3.1

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+9.009%; +9.021%]
  • 🟥 throughput [-37561.596op/s; -27285.719op/s] or [-9.284%; -6.744%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync net472

  • 🟥 allocated_mem [+295 bytes; +296 bytes] or [+10.163%; +10.175%]
  • 🟥 throughput [-10566.932op/s; -10310.674op/s] or [-12.063%; -11.770%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync net6.0

  • 🟥 allocated_mem [+191 bytes; +192 bytes] or [+9.052%; +9.064%]
  • 🟥 throughput [-8528.717op/s; -7684.748op/s] or [-5.794%; -5.220%]

scenario:Benchmarks.Trace.HttpClientBenchmark.SendAsync netcoreapp3.1

  • 🟥 allocated_mem [+191 bytes; +192 bytes] or [+7.267%; +7.279%]
  • 🟥 throughput [-14795.569op/s; -13264.686op/s] or [-11.741%; -10.526%]

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_AddEvent_Sampled net6.0

  • 🟩 throughput [+13095.762op/s; +15534.764op/s] or [+5.463%; +6.480%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472

  • 🟥 throughput [-13521.947op/s; -13043.097op/s] or [-16.033%; -15.465%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net6.0

  • 🟥 throughput [-11807.679op/s; -9028.740op/s] or [-9.925%; -7.589%]

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

  • 🟥 throughput [-15094.317op/s; -13439.703op/s] or [-15.348%; -13.665%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • 🟥 allocated_mem [+1.605KB; +1.605KB] or [+48.760%; +48.776%]
  • 🟥 execution_time [+311.675ms; +315.151ms] or [+154.664%; +156.389%]
  • 🟥 throughput [-60.916op/s; -56.257op/s] or [-10.960%; -10.122%]

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

  • 🟥 allocated_mem [+1.012KB; +1.012KB] or [+37.524%; +37.537%]
  • 🟥 execution_time [+374.290ms; +376.513ms] or [+295.712%; +297.469%]
  • 🟩 throughput [+74.689op/s; +78.513op/s] or [+9.848%; +10.352%]

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

  • 🟥 allocated_mem [+1.088KB; +1.088KB] or [+40.343%; +40.355%]
  • 🟥 execution_time [+391.962ms; +395.969ms] or [+346.871%; +350.418%]

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

  • 🟥 allocated_mem [+4.749KB; +4.750KB] or [+99.987%; +100.003%]
  • 🟥 throughput [-60175.176op/s; -59808.898op/s] or [-46.819%; -46.534%]

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

  • 🟥 allocated_mem [+3.872KB; +3.872KB] or [+81.884%; +81.895%]
  • 🟥 throughput [-62822.108op/s; -59010.873op/s] or [-45.857%; -43.075%]

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

  • 🟥 allocated_mem [+4.600KB; +4.600KB] or [+99.468%; +99.481%]
  • 🟥 throughput [-48291.498op/s; -46043.899op/s] or [-43.661%; -41.629%]

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

  • 🟥 allocated_mem [+1.372KB; +1.372KB] or [+111.007%; +111.023%]
  • 🟥 throughput [-284405.182op/s; -281201.164op/s] or [-29.039%; -28.712%]

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

  • 🟥 allocated_mem [+535 bytes; +536 bytes] or [+43.787%; +43.796%]
  • 🟩 execution_time [-26.201ms; -20.531ms] or [-11.684%; -9.156%]
  • 🟥 throughput [-115005.791op/s; -88314.602op/s] or [-12.286%; -9.435%]

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

  • 🟥 allocated_mem [+1.336KB; +1.336KB] or [+110.585%; +110.599%]
  • 🟥 throughput [-170825.387op/s; -154725.410op/s] or [-24.544%; -22.231%]

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

  • 🟥 allocated_mem [+3.378KB; +3.378KB] or [+89.003%; +89.017%]
  • 🟥 throughput [-72597.038op/s; -71829.637op/s] or [-48.857%; -48.341%]

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

  • 🟥 allocated_mem [+3.336KB; +3.336KB] or [+88.150%; +88.161%]
  • 🟥 throughput [-75274.471op/s; -72387.785op/s] or [-47.896%; -46.059%]

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

  • 🟥 allocated_mem [+3.264KB; +3.264KB] or [+88.493%; +88.506%]
  • 🟥 throughput [-56576.327op/s; -53910.540op/s] or [-45.070%; -42.947%]

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

  • 🟩 throughput [+210430.517op/s; +255449.379op/s] or [+7.017%; +8.518%]

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

  • 🟩 execution_time [-18.830ms; -14.492ms] or [-8.680%; -6.680%]

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

  • 🟩 allocated_mem [-13.759KB; -13.756KB] or [-42.324%; -42.316%]
  • 🟥 execution_time [+299.954ms; +300.658ms] or [+149.877%; +150.229%]
  • 🟩 throughput [+976.481op/s; +1006.898op/s] or [+10.785%; +11.121%]

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

  • 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
  • 🟥 execution_time [+299.575ms; +302.726ms] or [+151.076%; +152.666%]
  • 🟩 throughput [+2138.404op/s; +2351.724op/s] or [+16.356%; +17.987%]

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

  • 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
  • 🟥 execution_time [+299.818ms; +302.189ms] or [+151.025%; +152.220%]
  • 🟩 throughput [+1799.845op/s; +1930.028op/s] or [+17.377%; +18.633%]

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

  • 🟥 execution_time [+296.022ms; +297.113ms] or [+145.394%; +145.930%]
  • 🟩 throughput [+580.117op/s; +589.639op/s] or [+15.379%; +15.632%]

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

  • 🟥 execution_time [+297.241ms; +298.862ms] or [+145.310%; +146.103%]
  • 🟩 throughput [+2713.359op/s; +2761.411op/s] or [+39.420%; +40.118%]

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

  • 🟥 execution_time [+300.332ms; +301.252ms] or [+150.106%; +150.566%]
  • 🟩 throughput [+1362.696op/s; +1403.037op/s] or [+27.048%; +27.849%]

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

  • 🟩 execution_time [-146.533µs; -142.475µs] or [-30.085%; -29.252%]
  • 🟩 throughput [+853.087op/s; +880.309op/s] or [+41.549%; +42.875%]

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

  • 🟩 execution_time [-115.475µs; -87.440µs] or [-26.484%; -20.054%]
  • 🟩 throughput [+623.958op/s; +767.667op/s] or [+27.127%; +33.375%]

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

  • 🟩 execution_time [-133.440µs; -106.908µs] or [-28.590%; -22.905%]
  • 🟩 throughput [+670.567op/s; +793.173op/s] or [+30.955%; +36.614%]

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

  • 🟩 execution_time [-123.640µs; -119.396µs] or [-33.382%; -32.236%]
  • 🟩 throughput [+1295.520op/s; +1343.651op/s] or [+47.980%; +49.763%]

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

  • 🟩 execution_time [-94.651µs; -70.848µs] or [-30.217%; -22.618%]
  • 🟩 throughput [+1029.588op/s; +1238.875op/s] or [+32.095%; +38.619%]

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

  • 🟩 execution_time [-135.873µs; -113.451µs] or [-37.170%; -31.036%]
  • 🟩 throughput [+1296.686op/s; +1435.069op/s] or [+46.533%; +51.499%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

  • 🟥 execution_time [+299.549ms; +300.316ms] or [+149.506%; +149.889%]

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

  • unstable execution_time [+318.090ms; +387.838ms] or [+345.618%; +421.402%]

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

  • 🟥 execution_time [+354.896ms; +366.014ms] or [+269.469%; +277.911%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

  • unstable execution_time [+299.638ms; +352.036ms] or [+137.771%; +161.863%]
  • 🟥 throughput [-530.635op/s; -489.346op/s] or [-48.081%; -44.340%]

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

  • unstable execution_time [+144.274ms; +290.487ms] or [+61.484%; +123.793%]
  • 🟥 throughput [-669.520op/s; -586.009op/s] or [-44.657%; -39.087%]

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

  • 🟥 execution_time [+336.782ms; +344.541ms] or [+201.435%; +206.076%]
  • 🟥 throughput [-408.695op/s; -370.551op/s] or [-28.457%; -25.801%]

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

  • 🟩 execution_time [-158.766µs; -109.883µs] or [-8.043%; -5.566%]
  • 🟩 throughput [+31.712op/s; +44.393op/s] or [+6.260%; +8.763%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

  • 🟥 allocated_mem [+88 bytes; +89 bytes] or [+11.094%; +11.104%]
  • 🟥 execution_time [+299.644ms; +301.426ms] or [+150.895%; +151.792%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+11.101%; +11.112%]
  • 🟥 execution_time [+301.723ms; +304.122ms] or [+151.194%; +152.396%]
  • 🟥 throughput [-42096.185op/s; -31789.648op/s] or [-6.637%; -5.012%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+11.101%; +11.112%]
  • 🟥 execution_time [+301.560ms; +305.753ms] or [+151.491%; +153.597%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+10.235%; +10.247%]
  • 🟥 execution_time [+302.269ms; +303.944ms] or [+151.789%; +152.630%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+11.451%; +11.465%]
  • 🟥 execution_time [+298.210ms; +300.190ms] or [+147.452%; +148.431%]
  • 🟥 throughput [-73053.642op/s; -64798.434op/s] or [-11.770%; -10.440%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+10.469%; +10.481%]
  • 🟥 execution_time [+301.754ms; +306.149ms] or [+152.942%; +155.170%]
  • 🟥 throughput [-35139.104op/s; -25981.590op/s] or [-7.588%; -5.611%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

  • 🟥 allocated_mem [+88 bytes; +89 bytes] or [+10.268%; +10.280%]
  • 🟥 execution_time [+299.887ms; +303.277ms] or [+150.516%; +152.218%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+9.730%; +9.743%]
  • 🟥 execution_time [+301.130ms; +303.556ms] or [+150.086%; +151.295%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+9.730%; +9.743%]
  • 🟥 execution_time [+300.615ms; +303.137ms] or [+149.553%; +150.808%]
  • 🟥 throughput [-29056.063op/s; -22822.490op/s] or [-6.878%; -5.402%]

scenario:Benchmarks.Trace.ILoggerBenchmark.EnrichedLog net472

  • 🟥 allocated_mem [+88 bytes; +89 bytes] or [+5.504%; +5.513%]
  • 🟥 throughput [-15360.385op/s; -13411.144op/s] or [-6.177%; -5.393%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+5.160%; +5.169%]
  • 🟩 execution_time [-16.432ms; -12.766ms] or [-7.641%; -5.936%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+5.136%; +5.148%]

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

  • unstable execution_time [+11.780µs; +57.771µs] or [+2.910%; +14.270%]

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

  • 🟩 allocated_mem [-26.560KB; -26.536KB] or [-9.688%; -9.680%]
  • unstable execution_time [-50.842µs; +8.400µs] or [-10.049%; +1.660%]
  • unstable throughput [-15.067op/s; +196.468op/s] or [-0.752%; +9.804%]

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

  • unstable execution_time [-53.877µs; +5.296µs] or [-9.336%; +0.918%]

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

  • unstable execution_time [+5.503µs; +9.812µs] or [+13.007%; +23.192%]
  • 🟥 throughput [-4511.856op/s; -2708.941op/s] or [-18.993%; -11.404%]

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

  • unstable execution_time [-13.033µs; -4.705µs] or [-20.220%; -7.300%]
  • unstable throughput [+1169.791op/s; +2987.841op/s] or [+7.177%; +18.331%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

  • 🟥 execution_time [+301.887ms; +303.095ms] or [+152.591%; +153.201%]

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

  • 🟥 execution_time [+304.179ms; +307.437ms] or [+154.826%; +156.485%]

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

  • 🟥 execution_time [+299.515ms; +302.888ms] or [+149.944%; +151.633%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive net472

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+8.432%; +8.443%]
  • 🟥 throughput [-49917.674op/s; -48175.460op/s] or [-13.819%; -13.336%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+8.456%; +8.467%]

scenario:Benchmarks.Trace.RedisBenchmark.SendReceive netcoreapp3.1

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+8.456%; +8.466%]
  • 🟥 throughput [-34330.627op/s; -25409.436op/s] or [-8.125%; -6.014%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

  • 🟥 execution_time [+298.940ms; +300.693ms] or [+148.995%; +149.868%]
  • 🟥 throughput [-9433.514op/s; -7908.153op/s] or [-6.229%; -5.222%]

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

  • 🟥 allocated_mem [+88 bytes; +88 bytes] or [+5.502%; +5.512%]
  • 🟥 execution_time [+301.221ms; +302.768ms] or [+151.259%; +152.036%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+5.333%; +5.343%]
  • 🟥 execution_time [+303.136ms; +305.350ms] or [+153.731%; +154.854%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

  • 🟥 execution_time [+299.328ms; +300.548ms] or [+149.306%; +149.915%]
  • 🟩 throughput [+61076008.439op/s; +61415698.907op/s] or [+44.479%; +44.727%]

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

  • 🟥 execution_time [+420.348ms; +424.189ms] or [+522.778%; +527.554%]

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

  • 🟥 execution_time [+299.417ms; +300.799ms] or [+149.342%; +150.031%]
  • 🟩 throughput [+18050760.357op/s; +19037478.296op/s] or [+7.995%; +8.432%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net472

  • 🟥 throughput [-60119.913op/s; -56618.479op/s] or [-6.709%; -6.319%]

scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net472

  • 🟥 throughput [-67224.966op/s; -60113.231op/s] or [-6.154%; -5.503%]

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

  • 🟩 throughput [+37269.007op/s; +43013.648op/s] or [+6.767%; +7.810%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net472

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+14.421%; +14.433%]
  • 🟥 throughput [-75092.451op/s; -71291.871op/s] or [-10.990%; -10.434%]

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

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+13.576%; +13.589%]

scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin netcoreapp3.1

  • 🟥 allocated_mem [+87 bytes; +88 bytes] or [+13.576%; +13.587%]
  • 🟥 throughput [-84927.878op/s; -70176.022op/s] or [-11.858%; -9.798%]

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 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.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 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.Iast.StringAspectsBenchmark.StringConcatBenchmark net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan net6.0
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes net472
  • scenario:Benchmarks.Trace.SpanBenchmark.StartFinishTwoScopes netcoreapp3.1

@dd-trace-dotnet-ci-bot

dd-trace-dotnet-ci-bot Bot commented Sep 12, 2026 •
edited
Loading

Copy link
Copy Markdown

Execution-Time Benchmarks Report ⏱️

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

✅ No regressions detected

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

@leoromanovsky
Stabilize concurrent EVP transport test
41c584c 
Serialize the shared test request collector so concurrent sends cannot lose an observed request.\n\nEnvironment: Datadog workspace
@leoromanovsky
Merge master and preserve agentless activation with shared EVP transport
7eba078 
Keep the lazy exposure API and idempotent activation lifecycle from master while injecting shared discovery into the EVP transport. Cover activation, subscription cleanup, and source disposal.\n\nValidation: 658 feature flag and discovery tests pass on net10.0; scoped whitespace validation passes.\n\nEnvironment: Datadog workspace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area:ffe feature_flags

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@leoromanovsky