fix(docker connect): use connect_with_local_defaults on all platforms
since https://github.com/fussybeaver/bollard/pull/138 is merged, so we can use connect_with_local_defaults on all platforms
Regression Detector Results
Run ID: aa55a6bf-d68e-4f3a-b3c8-3e0548a92531 Metrics dashboard
Baseline: 75609314dd61b6923550411f60635f443a854f98 Comparison: 0cfa67c89531bb3a3776401bb6892b03d8149c8c
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
No significant changes in experiment optimization goals
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Experiments ignored for regressions
Regressions in experiments with settings containing erratic: true are ignored.
| perf | experiment | goal | Δ mean % | Δ mean % CI | links |
|---|---|---|---|---|---|
| ✅ | file_to_blackhole | egress throughput | +10.92 | [+3.68, +18.16] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | links |
|---|---|---|---|---|---|
| ✅ | file_to_blackhole | egress throughput | +10.92 | [+3.68, +18.16] | |
| ➖ | syslog_log2metric_humio_metrics | ingress throughput | +4.69 | [+4.51, +4.87] | |
| ➖ | http_text_to_http_json | ingress throughput | +2.72 | [+2.58, +2.85] | |
| ➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +2.13 | [+1.93, +2.33] | |
| ➖ | syslog_splunk_hec_logs | ingress throughput | +2.12 | [+2.00, +2.23] | |
| ➖ | http_elasticsearch | ingress throughput | +2.04 | [+1.86, +2.23] | |
| ➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +1.66 | [+1.50, +1.82] | |
| ➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.64 | [+1.40, +1.88] | |
| ➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +1.24 | [+1.13, +1.36] | |
| ➖ | socket_to_socket_blackhole | ingress throughput | +1.09 | [+1.00, +1.18] | |
| ➖ | datadog_agent_remap_blackhole | ingress throughput | +0.92 | [+0.82, +1.01] | |
| ➖ | http_to_http_acks | ingress throughput | +0.72 | [-0.54, +1.99] | |
| ➖ | syslog_loki | ingress throughput | +0.39 | [+0.31, +0.47] | |
| ➖ | http_to_http_noack | ingress throughput | +0.16 | [+0.08, +0.24] | |
| ➖ | http_to_s3 | ingress throughput | +0.08 | [-0.19, +0.35] | |
| ➖ | http_to_http_json | ingress throughput | +0.08 | [+0.02, +0.13] | |
| ➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.02 | [-0.08, +0.11] | |
| ➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.01 | [-0.13, +0.14] | |
| ➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.02 | [-0.10, +0.06] | |
| ➖ | otlp_http_to_blackhole | ingress throughput | -0.41 | [-0.53, -0.30] | |
| ➖ | fluent_elasticsearch | ingress throughput | -0.57 | [-1.06, -0.08] | |
| ➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.67 | [-0.78, -0.57] | |
| ➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.94 | [-1.07, -0.81] | |
| ➖ | otlp_grpc_to_blackhole | ingress throughput | -1.07 | [-1.19, -0.96] | |
| ➖ | syslog_humio_logs | ingress throughput | -1.57 | [-1.72, -1.43] | |
| ➖ | splunk_hec_route_s3 | ingress throughput | -1.89 | [-2.19, -1.58] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
Just a note that this seems to be blocked by macos tests failing when bollard is upgraded (see https://github.com/vectordotdev/vector/pull/20958).