Bumping viper to v1.14.0

[hush-hush]

What does this PR do?

Bumping viper to v1.14.0. New function IsConfigured added in 1.14.0 will be used in later PR.

Describe how you validated your changes

Running the CI is enough.

[agent-platform-auto-pr]

Package size comparison

Comparison with ancestor 6b70b84aebd4b35f9661d0fb3fe97dbe6f90dddf

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.02MB	⚠️	1271.63MB	1271.61MB	140.00MB
datadog-iot-agent-amd64-deb	0.00MB	⚠️	113.29MB	113.29MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	⚠️	78.41MB	78.41MB	10.00MB
datadog-heroku-agent-amd64-deb	0.01MB	⚠️	526.66MB	526.65MB	70.00MB
datadog-agent-x86_64-rpm	0.02MB	⚠️	1280.87MB	1280.85MB	140.00MB
datadog-agent-x86_64-suse	0.02MB	⚠️	1280.87MB	1280.85MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	⚠️	113.36MB	113.35MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	⚠️	113.35MB	113.35MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	⚠️	78.49MB	78.49MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	⚠️	78.49MB	78.49MB	10.00MB
datadog-agent-arm64-deb	0.02MB	⚠️	1005.69MB	1005.67MB	140.00MB
datadog-iot-agent-arm64-deb	0.01MB	⚠️	108.77MB	108.76MB	10.00MB
datadog-dogstatsd-arm64-deb	0.01MB	⚠️	55.65MB	55.64MB	10.00MB
datadog-agent-aarch64-rpm	0.02MB	⚠️	1014.91MB	1014.89MB	140.00MB
datadog-iot-agent-aarch64-rpm	0.01MB	⚠️	108.84MB	108.83MB	10.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 750ed69c-3c1b-460f-81e6-0280e3028c78

Baseline: 6b70b84
Comparison: 42683d9
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	tcp_syslog_to_blackhole	ingress throughput	+2.49	[+2.40, +2.58]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+2.12	[+2.00, +2.24]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.24	[+0.19, +0.29]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.16	[-0.65, +0.97]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.05	[-0.81, +0.90]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.08, +0.11]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.00	[-0.88, +0.89]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.00	[-0.77, +0.76]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.01	[-0.85, +0.84]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.04	[-0.79, +0.71]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.17	[-0.81, +0.46]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.24	[-0.70, +0.22]	1	Logs
➖	file_tree	memory utilization	-0.28	[-0.39, -0.16]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.60	[-1.33, +0.12]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.31	[-4.26, +1.64]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-1.55	[-2.26, -0.84]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_0ms_latency_http2	lost_bytes	9/10
❌	file_to_blackhole_300ms_latency	lost_bytes	9/10
❌	file_to_blackhole_500ms_latency	lost_bytes	9/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	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	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. 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.

3. 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_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.

[davidor]

👍 for container-platform files