[Serverless] Change serverless-init log level & remove noisy logs#42657
Conversation
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: d01a85a Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -0.01 | [-1.00, +0.98] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_memory | memory utilization | +2.99 | [+2.53, +3.44] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +2.76 | [+2.52, +3.00] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.79 | [+0.72, +0.86] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.72 | [+0.68, +0.76] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_logs | memory utilization | +0.68 | [+0.61, +0.75] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.49 | [+0.28, +0.69] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.48 | [+0.26, +0.71] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.39 | [+0.34, +0.43] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | +0.19 | [+0.03, +0.34] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.13 | [-0.10, +0.37] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.13 | [-0.49, +0.74] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.05 | [-0.55, +0.66] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.02 | [-0.58, +0.63] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.22, +0.24] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -0.01 | [-1.00, +0.98] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.05 | [-0.66, +0.55] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.07 | [-0.11, -0.03] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.16 | [-0.21, -0.11] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.52 | [-0.68, -0.36] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.73 | [-0.82, -0.63] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -1.08 | [-3.85, +1.68] | 1 | Logs bounds checks dashboard |
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_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.
- quality_gate_logs, 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: 10/10 replicas passed. Gate passed.
- 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_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 cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
| // Disable UDS listener for serverless environments - traces are sent via HTTP to localhost instead. | ||
| // This avoids noisy error logs. | ||
| pkgconfigsetup.Datadog().Set("apm_config.receiver_socket", "", model.SourceAgentRuntime) | ||
|
|
There was a problem hiding this comment.
In mode.go I also tried setting DD_APM_RECEIVER_SOCKET=""
But:
By default, empty environment variables are considered unset and will fall back to the next configuration source, unless AllowEmptyEnv is used.
(according to https://github.com/spf13/viper)
So this was the only working solution
rahulkaukuntla
left a comment
There was a problem hiding this comment.
LGTM for Agent Configuration-owned files
| // This commonly occurs in serverless environments like Cloud Run or Azure Container Apps | ||
| // where Kubernetes metadata is not available. | ||
| if strings.TrimSpace(valueFromConfig) == "" { | ||
| return map[string]map[string]string{} |
There was a problem hiding this comment.
should we gate this early return on detecting that this is running in a serverless environment? others may still care about the errors
There was a problem hiding this comment.
I don't think we can detect easily if we're in a serverless environment. Especially in sidecar mode--the sidecar has no special env vars to indicate we're in serverless.
Alternatively, I can add back a log but lower it to debug? What do you think?
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
offtoerrorerrorlog levelMotivation
#27083
https://datadoghq.atlassian.net/browse/SVLS-7891
Describe how you validated your changes
Manually
Additional Notes