Open andrewlock opened 1 week ago
Branch report: andrew/config-refactor/5-record-otel-telemetry
Commit report: 9302272
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 142 Passed, 0 Skipped, 1h 11m 27.35s Total Time
Execution-time results for samples comparing the following branches/commits:
Execution-time benchmarks measure the whole time it takes to execute a program. And are intended to measure the one-off costs. Cases where the execution time results for the PR are worse than latest master results are shown in red. The following thresholds were used for comparing the execution times:
Note that these results are based on a single point-in-time result for each branch. For full results, see the dashboard.
Graphs show the p99 interval based on the mean and StdDev of the test run, as well as the mean value of the run (shown as a diamond below the graph).
gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (74ms) : 62, 86
. : milestone, 74,
master - mean (72ms) : 63, 81
. : milestone, 72,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (907ms) : 887, 926
. : milestone, 907,
master - mean (895ms) : 874, 916
. : milestone, 895,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (110ms) : 106, 114
. : milestone, 110,
master - mean (109ms) : 106, 113
. : milestone, 109,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (633ms) : 612, 654
. : milestone, 633,
master - mean (634ms) : 618, 651
. : milestone, 634,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (93ms) : 90, 96
. : milestone, 93,
master - mean (93ms) : 90, 96
. : milestone, 93,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (594ms) : 576, 612
. : milestone, 594,
master - mean (591ms) : 572, 610
. : milestone, 591,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (191ms) : 188, 195
. : milestone, 191,
master - mean (192ms) : 188, 196
. : milestone, 192,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (1,014ms) : 980, 1047
. : milestone, 1014,
master - mean (1,003ms) : 974, 1031
. : milestone, 1003,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (276ms) : 272, 280
. : milestone, 276,
master - mean (275ms) : 270, 280
. : milestone, 275,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (831ms) : 805, 857
. : milestone, 831,
master - mean (823ms) : 791, 855
. : milestone, 823,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5717) - mean (266ms) : 263, 270
. : milestone, 266,
master - mean (264ms) : 260, 269
. : milestone, 264,
section CallTarget+Inlining+NGEN
This PR (5717) - mean (809ms) : 782, 837
. : milestone, 809,
master - mean (811ms) : 780, 843
. : milestone, 811,
Benchmarks for #5717 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Benchmarks for #5717 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Throughput results for AspNetCoreSimpleController comparing the following branches/commits:
Cases where throughput results for the PR are worse than latest master (5% drop or greater), results are shown in red.
Note that these results are based on a single point-in-time result for each branch. For full results, see one of the many, many dashboards!
gantt
title Throughput Linux x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5717) (11.820M) : 0, 11819641
master (11.941M) : 0, 11940953
benchmarks/2.9.0 (11.959M) : 0, 11959218
section Automatic
This PR (5717) (7.984M) : 0, 7983558
master (8.126M) : 0, 8125742
benchmarks/2.9.0 (8.424M) : 0, 8423539
section Trace stats
master (8.463M) : 0, 8462913
section Manual
This PR (5717) (10.213M) : 0, 10212632
master (10.295M) : 0, 10294729
section Manual + Automatic
This PR (5717) (7.517M) : 0, 7517347
master (7.548M) : 0, 7547543
section Version Conflict
master (6.848M) : 0, 6848367
gantt
title Throughput Linux arm64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5717) (9.382M) : 0, 9382173
master (9.671M) : 0, 9670503
benchmarks/2.9.0 (9.647M) : 0, 9646678
section Automatic
This PR (5717) (6.734M) : 0, 6733673
master (6.513M) : 0, 6513280
section Trace stats
master (6.824M) : 0, 6824339
section Manual
This PR (5717) (8.272M) : 0, 8272072
master (8.189M) : 0, 8189017
section Manual + Automatic
This PR (5717) (6.213M) : 0, 6213035
master (6.236M) : 0, 6235985
section Version Conflict
master (5.631M) : 0, 5631298
gantt
title Throughput Windows x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5717) (10.189M) : 0, 10188971
master (10.108M) : 0, 10107819
benchmarks/2.9.0 (10.154M) : 0, 10153990
section Automatic
This PR (5717) (7.302M) : 0, 7301745
master (7.230M) : 0, 7230329
benchmarks/2.9.0 (7.563M) : 0, 7562893
section Trace stats
master (7.514M) : 0, 7513930
section Manual
This PR (5717) (9.161M) : 0, 9161480
master (8.979M) : 0, 8979416
section Manual + Automatic
This PR (5717) (7.002M) : 0, 7001539
master (6.821M) : 0, 6820517
section Version Conflict
master (6.181M) : 0, 6181437
Summary of changes
Records logs and metrics for when otel config is overriden by datadog config, or when it's invalid
Reason for change
This was originally part of https://github.com/DataDog/dd-trace-dotnet/pull/5661, but wasn't possible due to concerns with the fact
ConfigurationBuilder
is used in critical "startup" paths for the tracer, so can result in recursion if we're not careful.Implementation details
The crux of the implementation is that we "store" error and metrics for writing at the point we know it's safe. This is similar to what we already do for configuration telemetry.
(Technically I think we Could directly access the
TelemetryFactory.Metrics
, but this is "safer", and makes it easier to test we're sending the right metricsTest coverage
Added unit tests to all of the existing settings tests where we override configuration to confirm that it works as expected
Other details
The metrics etc are all ported from https://github.com/DataDog/dd-trace-dotnet/pull/5661, but there are currently some issues with the proposed values:
.
. I would suggest changing these to be lowercase and replacing.
with_
, but either way this should happen after they've been OK'd in the intake.Part of a big ole stack: