-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(docs): improve source data_dir docs #19596
Conversation
Your preview site for the vector.dev will be ready in a few minutes, please allow time for it to build. Heres your preview link: |
Your preview site for the Rust Doc will be ready in a few minutes, please allow time for it to build. Heres your preview link: |
Datadog ReportBranch report: ✅ 0 Failed, 2092 Passed, 0 Skipped, 1m 25s Wall Time |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
29b0d29
to
e3fdf66
Compare
Regression Detector ResultsRun ID: 846afa6b-5b84-47d4-88da-2346c84de847 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +3.48 | [+3.34, +3.61] |
➖ | http_to_http_acks | ingress throughput | +1.33 | [+0.01, +2.64] |
➖ | file_to_blackhole | egress throughput | +1.19 | [-1.35, +3.73] |
➖ | otlp_http_to_blackhole | ingress throughput | +1.00 | [+0.86, +1.15] |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +0.98 | [+0.89, +1.07] |
➖ | syslog_loki | ingress throughput | +0.95 | [+0.90, +1.00] |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +0.57 | [+0.49, +0.65] |
➖ | socket_to_socket_blackhole | ingress throughput | +0.56 | [+0.49, +0.64] |
➖ | splunk_hec_route_s3 | ingress throughput | +0.42 | [-0.07, +0.90] |
➖ | syslog_humio_logs | ingress throughput | +0.39 | [+0.30, +0.49] |
➖ | http_to_http_noack | ingress throughput | +0.11 | [+0.02, +0.20] |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.03 | [-0.05, +0.12] |
➖ | http_to_http_json | ingress throughput | +0.02 | [-0.05, +0.10] |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.00 | [-0.14, +0.15] |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.16, +0.16] |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.01 | [-0.12, +0.10] |
➖ | http_elasticsearch | ingress throughput | -0.01 | [-0.08, +0.06] |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -0.03 | [-0.14, +0.07] |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.04 | [-0.13, +0.04] |
➖ | enterprise_http_to_http | ingress throughput | -0.13 | [-0.21, -0.06] |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.19 | [-0.31, -0.07] |
➖ | http_to_s3 | ingress throughput | -0.24 | [-0.52, +0.03] |
➖ | fluent_elasticsearch | ingress throughput | -0.54 | [-1.01, -0.08] |
➖ | syslog_splunk_hec_logs | ingress throughput | -0.96 | [-1.03, -0.88] |
➖ | http_text_to_http_json | ingress throughput | -1.05 | [-1.18, -0.92] |
➖ | datadog_agent_remap_blackhole | ingress throughput | -1.13 | [-1.24, -1.03] |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.46 | [-1.60, -1.31] |
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".
* chore(docs): improve source data_dir docs * fix doc content * regen docs
No description provided.