Simplify AGENTS.md

[bouwkast]

Summary of changes

Deletes most of AGENTS.md

Reason for change

Locally, I have been running overrides of the AGENTS.md with an empty file and have found that I have reduced my token usage while also improving the quality of the output that I get with various models.

Implementation details

Delete many lines I left some that may be reasonable.

Test coverage

We will see

Other details

[vandonr]

would it make sense to keep the reference to docs/ and tell the agent to look in it for more details ? Or maybe it finds it itself ?

[pr-commenter]

LLM Validation

LLM Validation Gate — dotnet-tracer-agent

🔴 FAIL

• 1 blocking case(s) confidently regressed (win-rate below 45% with the CI upper bound below 55%, or the CI entirely below 50%) — these must not regress.
• Confirmation pass: re-ran 2 case(s) flagged as a confident regression (+8 runs each); 1 reproduced after pooling and still block.

Analysis

Changed instruction file(s): AGENTS.md.

Blocking — 3 case(s) regressed; the gate failed on the worst below.

• dotnet-tracer-nuget-scope-hallucination-008: won 33% of blind comparisons, quality -4.1.
  • Asked: Does the Datadog.Trace NuGet package include the auto-instrumentation code and native profiler? A teammate wants to reference it to get automatic spans.
  • Baseline answer: No — and referencing it won't give your teammate automatic spans. Per the repo's NuGet package architecture: the Datadog.Trace NuGet package ships only the manual instrumentation API (Datadog.Trace.Manual.dll). It does not include auto-instrumentation code or the native profiler binaries. Here's the split:
  • Candidate answer: No — and this is a common mix-up. Straight from the repo's own package docs: Datadog.Trace contains only the custom (manual) instrumentation library. It does not include the auto-instrumentation code or the native binaries. As of v3.0.0 it explicitly requires that automatic instrumentation be configured
• dotnet-tracer-logging-terminology-004: won 42% of blind comparisons, quality -5.7.
  • Asked: Write the log message for when the entire Datadog product is being disabled at startup, and briefly say which terms to use or avoid.
  • Baseline answer: Based on the project's Logging Guidelines, here's the message: csharp "The Datadog SDK has been disabled" Terms to use / avoid: - Use "Datadog SDK" — this is the customer-facing term for the whole monitoring solution, which is exactly what's being disabled at startup here. - Avoid "Profiler" — it's
  • Candidate answer: Based on the codebase conventions, the umbrella term already used for the whole product in these native startup paths is "Datadog SDK" (see shared/src/Datadog.Trace.ClrProfiler.Native/cor_profiler.cpp:133-291, e.g. "CorProfiler::Initialize Datadog SDK disabled: ..."). ## Log message ```cpp Log::Info("Datadog
• dotnet-tracer-confirm-instrumentation-011: won 44% of blind comparisons, quality -0.4.
  • Asked: How can I confirm, from this repo and its runtime logs, whether a given library method is auto-instrumented — both where the instrumentation is declared in
  • Baseline answer: Both investigations are back and match what I verified directly in the native code. Here's the complete picture. ## Confirming auto-instrumentation of a library method There are two independent things to check: (A) that it's declared in source, and (B) that the rewrite actually happened at runtime. They live
  • Candidate answer: Both investigations are complete. Here's how to confirm auto-instrumentation for a given library method in this repo — the source declaration side and the runtime-proof side. ## 1. Where it's declared in source Auto-instrumentation is declared with the [InstrumentMethod] attribute on an integration class. -

Results

• Pairwise win-rate: 42% [38%–47%] — candidate's share of blind comparisons (90% CI; spanning 50% = no clear difference)
• Overall quality: 85.7 → 83.2 (/100, -2.5)
• Bad signals introduced (advisory): 0
• Blocking-case regressions: 3

Cases

Case	Mode	Quality Δ	Win-rate (90% CI)	Safety
dotnet-tracer-repo-nav-integration-001	block	+4.2	53% [48%–58%]	ok
dotnet-tracer-logging-terminology-004 🟡	block	-5.7	42% [32%–52%]	ok
dotnet-tracer-nuget-scope-hallucination-008 🔴	block	-4.1	33% [23%–42%]	ok
dotnet-tracer-confirm-instrumentation-011 🟡	block	-0.4	44% [37%–51%]	ok
dotnet-tracer-control-context-propagation-016	warn	-1.5	50% [39%–61%]	ok

_{Per-dimension scores, token usage, latency, and estimated cost are in the CI job logs.}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-04 15:49:12

Comparing candidate commit b2c3d12 in PR branch steven/revamp-agents with baseline commit f2eed57 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 1 performance regressions! Performance is the same for 70 metrics, 1 unstable metrics, 64 known flaky benchmarks, 62 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 [-25598.875op/s; -19367.389op/s] or [-7.210%; -5.455%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

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

• unstable execution_time [-28.811ms; -7.424ms] or [-14.388%; -3.708%]

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

• 🟥 throughput [-24309.076op/s; -19909.025op/s] or [-8.097%; -6.632%]

scenario:Benchmarks.Trace.ActivityBenchmark.StartStopWithChild net472

• 🟥 throughput [-7189.526op/s; -6647.418op/s] or [-8.525%; -7.882%]

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

• unstable execution_time [-33.173ms; -8.849ms] or [-16.685%; -4.451%]
• 🟥 throughput [-8820.650op/s; -7139.867op/s] or [-8.969%; -7.260%]

scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net472

• 🟥 allocated_mem [+1.605KB; +1.605KB] or [+48.760%; +48.776%]
• 🟥 execution_time [+308.189ms; +310.977ms] or [+152.934%; +154.318%]
• 🟥 throughput [-57.009op/s; -52.764op/s] or [-10.257%; -9.493%]

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

• 🟥 allocated_mem [+1.011KB; +1.011KB] or [+37.485%; +37.498%]
• 🟥 execution_time [+375.256ms; +376.205ms] or [+296.476%; +297.225%]
• 🟩 throughput [+68.910op/s; +70.560op/s] or [+9.086%; +9.303%]

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

• 🟥 allocated_mem [+1.090KB; +1.090KB] or [+40.417%; +40.429%]
• 🟥 execution_time [+394.607ms; +399.832ms] or [+349.212%; +353.836%]

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

• 🟥 allocated_mem [+4.725KB; +4.726KB] or [+99.482%; +99.497%]
• 🟥 throughput [-60573.769op/s; -60166.758op/s] or [-47.130%; -46.813%]

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

• 🟥 allocated_mem [+3.848KB; +3.848KB] or [+81.379%; +81.391%]
• 🟩 execution_time [-15.611ms; -11.434ms] or [-7.291%; -5.340%]
• 🟥 throughput [-60392.351op/s; -57628.497op/s] or [-44.083%; -42.066%]

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

• 🟥 allocated_mem [+4.576KB; +4.576KB] or [+98.954%; +98.966%]
• 🟥 throughput [-49405.984op/s; -47156.187op/s] or [-44.669%; -42.635%]

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

• 🟥 allocated_mem [+1.348KB; +1.348KB] or [+109.063%; +109.078%]
• 🟥 throughput [-298713.443op/s; -295553.939op/s] or [-30.500%; -30.178%]

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

• 🟥 allocated_mem [+511 bytes; +512 bytes] or [+41.822%; +41.834%]
• 🟩 execution_time [-25.703ms; -20.851ms] or [-11.462%; -9.299%]
• 🟥 throughput [-117429.707op/s; -94842.000op/s] or [-12.545%; -10.132%]

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

• 🟥 allocated_mem [+1.312KB; +1.312KB] or [+108.600%; +108.616%]
• 🟥 throughput [-167866.736op/s; -151983.502op/s] or [-24.119%; -21.837%]

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

• 🟥 allocated_mem [+3.378KB; +3.378KB] or [+89.003%; +89.017%]
• 🟥 throughput [-72440.113op/s; -71679.281op/s] or [-48.751%; -48.239%]

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

• 🟥 allocated_mem [+3.336KB; +3.336KB] or [+88.150%; +88.161%]
• 🟥 throughput [-72736.472op/s; -69850.866op/s] or [-46.281%; -44.445%]

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

• 🟥 allocated_mem [+3.264KB; +3.264KB] or [+88.493%; +88.506%]
• 🟥 throughput [-56321.460op/s; -53699.215op/s] or [-44.867%; -42.778%]

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

• 🟩 throughput [+306102.362op/s; +328659.188op/s] or [+10.207%; +10.959%]

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

• 🟩 execution_time [-18.983ms; -14.645ms] or [-8.751%; -6.751%]

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

• 🟩 allocated_mem [-13.759KB; -13.757KB] or [-42.326%; -42.318%]
• 🟥 execution_time [+300.312ms; +300.974ms] or [+150.056%; +150.386%]
• 🟩 throughput [+994.000op/s; +1014.151op/s] or [+10.979%; +11.201%]

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

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• 🟥 execution_time [+298.677ms; +310.534ms] or [+150.624%; +156.603%]
• 🟩 throughput [+2130.765op/s; +2497.015op/s] or [+16.297%; +19.098%]

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

• 🟩 allocated_mem [-13.722KB; -13.718KB] or [-42.341%; -42.329%]
• 🟥 execution_time [+298.991ms; +309.733ms] or [+150.608%; +156.019%]
• 🟩 throughput [+1703.392op/s; +1940.912op/s] or [+16.445%; +18.739%]

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

• 🟥 execution_time [+296.207ms; +297.109ms] or [+145.485%; +145.928%]
• 🟩 throughput [+586.094op/s; +594.826op/s] or [+15.538%; +15.769%]

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

• 🟥 execution_time [+296.553ms; +298.021ms] or [+144.974%; +145.692%]
• 🟩 throughput [+2687.547op/s; +2726.332op/s] or [+39.045%; +39.609%]

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

• 🟥 execution_time [+301.973ms; +303.324ms] or [+150.926%; +151.601%]
• 🟩 throughput [+1368.407op/s; +1388.165op/s] or [+27.162%; +27.554%]

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

• 🟩 execution_time [-147.586µs; -143.558µs] or [-30.301%; -29.474%]
• 🟩 throughput [+862.350op/s; +889.272op/s] or [+42.000%; +43.312%]

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

• 🟩 execution_time [-136.100µs; -109.411µs] or [-31.215%; -25.093%]
• 🟩 throughput [+831.575op/s; +954.390op/s] or [+36.154%; +41.493%]

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

• 🟩 execution_time [-141.869µs; -119.763µs] or [-30.396%; -25.660%]
• 🟩 throughput [+768.932op/s; +853.941op/s] or [+35.495%; +39.420%]

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

• 🟩 execution_time [-126.433µs; -122.079µs] or [-34.136%; -32.961%]
• 🟩 throughput [+1338.688op/s; +1390.403op/s] or [+49.579%; +51.494%]

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

• 🟩 execution_time [-100.852µs; -77.262µs] or [-32.197%; -24.666%]
• 🟩 throughput [+1153.153op/s; +1354.509op/s] or [+35.947%; +42.224%]

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

• 🟩 execution_time [-136.043µs; -113.301µs] or [-37.216%; -30.995%]
• 🟩 throughput [+1294.085op/s; +1443.724op/s] or [+46.440%; +51.810%]

scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net472

• 🟥 execution_time [+299.401ms; +300.115ms] or [+149.432%; +149.788%]

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

• 🟥 execution_time [+409.598ms; +415.310ms] or [+445.045%; +451.252%]
• 🟩 throughput [+636.267op/s; +826.691op/s] or [+5.228%; +6.793%]

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

• unstable execution_time [+241.340ms; +307.269ms] or [+183.247%; +233.307%]

scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472

• unstable execution_time [+313.411ms; +348.934ms] or [+144.103%; +160.437%]
• 🟥 throughput [-508.904op/s; -472.206op/s] or [-46.112%; -42.787%]

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

• unstable execution_time [+207.547ms; +340.767ms] or [+88.448%; +145.220%]
• 🟥 throughput [-673.207op/s; -589.444op/s] or [-44.903%; -39.316%]

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

• 🟥 allocated_mem [+2.283KB; +2.287KB] or [+5.392%; +5.400%]
• 🟥 execution_time [+321.230ms; +335.938ms] or [+192.133%; +200.930%]
• 🟥 throughput [-401.486op/s; -365.042op/s] or [-27.955%; -25.417%]

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

• 🟩 execution_time [-187.304µs; -136.730µs] or [-9.488%; -6.926%]
• 🟩 throughput [+39.360op/s; +53.780op/s] or [+7.770%; +10.617%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearch net472

• 🟥 execution_time [+302.901ms; +304.450ms] or [+152.535%; +153.315%]

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

• 🟥 execution_time [+301.374ms; +303.332ms] or [+151.019%; +152.000%]

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

• 🟥 execution_time [+301.706ms; +304.910ms] or [+151.564%; +153.174%]

scenario:Benchmarks.Trace.ElasticsearchBenchmark.CallElasticsearchAsync net472

• 🟥 execution_time [+300.724ms; +302.341ms] or [+151.014%; +151.826%]

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

• 🟥 execution_time [+298.713ms; +300.924ms] or [+147.700%; +148.794%]

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

• 🟥 execution_time [+302.022ms; +306.308ms] or [+153.078%; +155.250%]

scenario:Benchmarks.Trace.GraphQLBenchmark.ExecuteAsync net472

• 🟥 execution_time [+303.579ms; +306.347ms] or [+152.369%; +153.759%]

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

• 🟥 execution_time [+298.810ms; +302.695ms] or [+148.929%; +150.866%]
• 🟩 throughput [+37277.909op/s; +41429.196op/s] or [+7.402%; +8.226%]

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

• 🟥 execution_time [+299.605ms; +302.308ms] or [+149.051%; +150.395%]

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

• 🟩 execution_time [-16.664ms; -13.006ms] or [-7.749%; -6.048%]

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

• unstable execution_time [+12.599µs; +57.835µs] or [+3.112%; +14.286%]

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

• 🟩 allocated_mem [-19.834KB; -19.810KB] or [-7.235%; -7.226%]
• unstable execution_time [-35.618µs; +20.229µs] or [-7.040%; +3.998%]

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

• 🟩 allocated_mem [-24.692KB; -24.673KB] or [-9.001%; -8.994%]
• unstable execution_time [-63.405µs; -2.872µs] or [-10.988%; -0.498%]

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

• unstable execution_time [+6.607µs; +11.163µs] or [+15.618%; +26.387%]
• 🟥 throughput [-4983.276op/s; -3102.243op/s] or [-20.978%; -13.059%]

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

• unstable execution_time [-13.574µs; -5.112µs] or [-21.060%; -7.931%]
• unstable throughput [+1341.725op/s; +3189.812op/s] or [+8.232%; +19.571%]

scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog net472

• 🟥 execution_time [+302.104ms; +303.154ms] or [+152.700%; +153.231%]

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

• 🟥 execution_time [+299.545ms; +301.954ms] or [+152.468%; +153.693%]

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

• 🟥 execution_time [+299.603ms; +301.923ms] or [+149.988%; +151.150%]

scenario:Benchmarks.Trace.SerilogBenchmark.EnrichedLog net472

• 🟥 execution_time [+300.909ms; +303.084ms] or [+149.976%; +151.060%]

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

• 🟥 execution_time [+301.573ms; +303.527ms] or [+151.436%; +152.417%]

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

• 🟥 execution_time [+302.369ms; +304.828ms] or [+153.342%; +154.589%]

scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net472

• 🟥 execution_time [+299.905ms; +301.020ms] or [+149.594%; +150.150%]
• 🟩 throughput [+60789108.536op/s; +61182047.130op/s] or [+44.270%; +44.557%]

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

• unstable execution_time [+340.282ms; +398.503ms] or [+423.201%; +495.610%]

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

• 🟥 execution_time [+299.004ms; +300.169ms] or [+149.136%; +149.717%]

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

• 🟩 throughput [+48934.286op/s; +70018.017op/s] or [+5.664%; +8.104%]

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

• 🟩 throughput [+69192.802op/s; +77905.630op/s] or [+6.872%; +7.737%]

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

• 🟩 throughput [+51924.026op/s; +58996.067op/s] or [+9.428%; +10.713%]

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

• 🟩 throughput [+65326.820op/s; +83347.967op/s] or [+7.299%; +9.312%]

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