-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Re-add code to print restarted container logs in k8s e2e tests #39217
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?
Re-add code to print restarted container logs in k8s e2e tests #39217
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: f065bed Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_cpu | % cpu utilization | -3.71 | [-6.70, -0.73] | 1 | Logs |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_idle | memory utilization | +0.55 | [+0.51, +0.59] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | +0.45 | [+0.38, +0.52] | 1 | Logs |
➖ | file_tree | memory utilization | +0.26 | [+0.22, +0.29] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.25 | [-2.53, +3.03] | 1 | Logs bounds checks dashboard |
➖ | otlp_ingest_logs | memory utilization | +0.06 | [-0.07, +0.18] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.03 | [-0.57, +0.64] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.31, +0.33] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.00 | [-0.60, +0.60] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.02, +0.01] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.01 | [-0.65, +0.64] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.02 | [-0.16, +0.12] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.06 | [-0.67, +0.55] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.17 | [-0.29, -0.05] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.33 | [-0.37, -0.29] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.52 | [-0.61, -0.43] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.60 | [-0.65, -0.55] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.95 | [-1.01, -0.89] | 1 | Logs |
➖ | quality_gate_metrics_logs | memory utilization | -2.14 | [-2.53, -1.75] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_cpu | % cpu utilization | -3.71 | [-6.70, -0.73] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | 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_1000ms_latency | 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_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 |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_metrics_logs | memory_usage | 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
✅ Passed. All Quality Gates passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 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 Successful checksInfo
|
What does this PR do?
Re-add the logic originally added here to display the logs of restarted containers as part of the k8s e2e tests
Motivation
In response to failing e2e tests after the introduction of this change (related incident). Unfortunately, the nature of the break is such that no pod logs are actually being reported by the crashing pod (confirmed by deploying the problematic version to an EKS cluster and running kubectl manually to see the logs)
But, you can see that, if there were log, they WOULD have been captured, in the output of this job
Describe how you validated your changes
See note in motivation, codepath hit as part of this failing job, but the break itself resulted in no logs so it doesn't help in this one case
Possible Drawbacks / Trade-offs
Additional Notes