-
Notifications
You must be signed in to change notification settings - Fork 1.3k
chore(deps): update integrations-core digest to 29d756d #37958
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
base: main
Are you sure you want to change the base?
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: e7b7917 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_memory | memory utilization | +0.87 | [+0.78, +0.95] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.71 | [-0.13, +1.56] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.60 | [+0.48, +0.72] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.58 | [+0.42, +0.74] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.47 | [+0.41, +0.52] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.39 | [+0.26, +0.52] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.11 | [-0.01, +0.23] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.06 | [-0.55, +0.66] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.04 | [-0.20, +0.28] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.03 | [-0.56, +0.62] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.02 | [-0.25, +0.29] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.01 | [-0.02, +0.04] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.01 | [-0.59, +0.58] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.01 | [-0.57, +0.55] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.02 | [-0.63, +0.60] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.04 | [-0.60, +0.52] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.14 | [-0.73, +0.44] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.20 | [-0.27, -0.14] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.65 | [-0.81, -0.49] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.67 | [-3.68, +2.35] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.65 | [-1.72, -1.58] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -2.07 | [-4.82, +0.68] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle_all_features | memory utilization | -4.90 | [-5.02, -4.78] | 1 | Logs bounds checks dashboard |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_logs | memory_usage | 6/10 | bounds checks dashboard |
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
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
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".
CI Pass/Fail Decision
❌ Failed. Some Quality Gates were violated.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 6/10 replicas passed. Failed 4 which is > 0. Gate FAILED.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Static quality checks❌ Please find below the results from static quality gates Error
Gate failure full details
Static quality gates prevent the PR to merge! You can check the static quality gates confluence page for guidance. We also have a toolbox page available to list tools useful to debug the size increase. Successful checksInfo
|
4a7b776
to
b77cd1f
Compare
b77cd1f
to
9e062ec
Compare
9e062ec
to
afac4f5
Compare
afac4f5
to
efac585
Compare
efac585
to
ff1f11c
Compare
ff1f11c
to
8a6698e
Compare
8a6698e
to
153c8e1
Compare
This PR contains the following updates:
5cc1053
->29d756d
Configuration
📅 Schedule: Branch creation - Between 02:00 AM and 06:59 AM, only on Monday and Wednesday ( * 2-6 * * 1,3 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.