Closed NachoEchevarria closed 4 weeks ago
Branch report: nacho/AvoidReportingUnknownMatcherErrors
Commit report: df29b01
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 358479 Passed, 2048 Skipped, 15h 34m 10.8s 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).
Benchmarks for #5955 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 (5955) (11.239M) : 0, 11238560
master (11.247M) : 0, 11246521
benchmarks/2.9.0 (11.120M) : 0, 11120231
section Automatic
This PR (5955) (7.492M) : 0, 7491949
master (7.508M) : 0, 7508439
benchmarks/2.9.0 (7.874M) : 0, 7874046
section Trace stats
master (7.707M) : 0, 7707332
section Manual
master (11.233M) : 0, 11232811
section Manual + Automatic
This PR (5955) (6.896M) : 0, 6895505
master (6.892M) : 0, 6891553
section DD_TRACE_ENABLED=0
master (10.225M) : 0, 10225326
gantt
title Throughput Linux arm64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5955) (9.503M) : 0, 9503007
benchmarks/2.9.0 (9.342M) : 0, 9341974
section Automatic
This PR (5955) (6.614M) : 0, 6614083
section Manual + Automatic
This PR (5955) (6.055M) : 0, 6055040
gantt
title Throughput Windows x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5955) (10.031M) : 0, 10030807
master (10.060M) : 0, 10059520
benchmarks/2.9.0 (10.105M) : 0, 10105239
section Automatic
This PR (5955) (6.684M) : 0, 6684420
master (6.690M) : 0, 6690107
benchmarks/2.9.0 (7.518M) : 0, 7517801
section Trace stats
master (7.324M) : 0, 7324117
section Manual
master (10.131M) : 0, 10131126
section Manual + Automatic
This PR (5955) (6.129M) : 0, 6129437
master (6.279M) : 0, 6279338
section DD_TRACE_ENABLED=0
master (9.441M) : 0, 9441325
Benchmarks for #5955 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Thanks for you reviews!
Summary of changes
The unknown matcher error happens when a new operator is added and it is not supported by the WAF, so sending this particular error is causing a lot of noise because old versions of the WAF will return that error that actually is supported in newer versions. We already write warnings for this situation, but we are also reporting errors that are not actually errors, Which is generating a lot of noise. In particular, we return errors in the remote config operations and we add error tags to the span.
This PR corrects this.
Reason for change
It was reported and requested.
Implementation details
Test coverage
Other details