[Backport 7.74.x] privileged logs: Handle unsearchable directories#44215
[Backport 7.74.x] privileged logs: Handle unsearchable directories#44215dd-mergequeue[bot] merged 1 commit into7.74.xfrom
Conversation
In any directory in the path of a configured log file does not have executable (search) permissions, it does not get tailed even with privileged logs enabled since a stat(2) call from the file launcher fails and the logs agent never gets to the point where it calls into system-probe. Fix this by having that stat(2) call too fallback to system-probe if privileged logs is enabled. https://datadoghq.atlassian.net/browse/DSCVR-288 Unit and E2E tests have been modified to test this case. Co-authored-by: vincent.whitchurch <vincent.whitchurch@datadoghq.com> (cherry picked from commit d81746c) (Manually fixed conflict in pkg/logs/launchers/file/launcher_test.go due to "Replace uses of `fmt.Sprintf` and `fmt.Errorf` with better alternatives (#43413) not being present on 7.74.x)
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: b2ffa5d Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +0.14 | [-2.91, +3.18] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_memory | memory utilization | +1.93 | [+1.78, +2.09] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.85 | [+0.64, +1.07] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.28 | [+0.19, +0.37] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | +0.14 | [-2.91, +3.18] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.13 | [+0.08, +0.17] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle | memory utilization | +0.12 | [+0.07, +0.16] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.12, +0.14] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.06, +0.07] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.00 | [-0.37, +0.37] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.00 | [-0.05, +0.05] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.01 | [-0.14, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.06, +0.03] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.04 | [-0.44, +0.37] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.05 | [-0.44, +0.34] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.13 | [-0.34, +0.09] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.13 | [-0.36, +0.10] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.14 | [-0.36, +0.08] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.22 | [-0.37, -0.07] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.24 | [-0.34, -0.14] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.30 | [-0.36, -0.24] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.41 | [-0.46, -0.35] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.52 | [-0.68, -0.36] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -1.39 | [-2.83, +0.06] | 1 | Logs bounds checks dashboard |
Bounds Checks: ❌ Failed
| 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 | lost_bytes | 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 | 9/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
❌ Failed. Some Quality Gates were violated.
- 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 intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
- 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 intake_connections: 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 cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
Backports #43747. The backport had to be performed manually since there was a conflict in
pkg/logs/launchers/file/launcher_test.godue to "Replace uses offmt.Sprintfandfmt.Errorfwith better alternatives" (#43413) not being present on 7.74.x. No other files had conflicts.In any directory in the path of a configured log file does not have executable (search) permissions, it does not get tailed even with privileged logs enabled since a stat(2) call from the file launcher fails and the logs agent never gets to the point where it calls into system-probe. Fix this by having that stat(2) call too fallback to system-probe if privileged logs is enabled.
https://datadoghq.atlassian.net/browse/DSCVR-288
Unit and E2E tests have been modified to test this case.
(cherry picked from commit d81746c)
(Manually fixed conflict in pkg/logs/launchers/file/launcher_test.go
due to "Replace uses of
fmt.Sprintfandfmt.Errorfwith betteralternatives (#43413) not being present on 7.74.x)