[CWS] onboard second batch of fs constants to the fetcher

[paulcacheux]

What does this PR do?

second part of #32700

Motivation

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=52380663 --os-family=ubuntu

Note: This applies to commit 6f1383a

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 44411ed7c91af334aab2d44b3b0a7dda4db0d9d6

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-aarch64-rpm	0.11MB	⚠️	950.18MB	950.07MB	140.00MB
datadog-agent-arm64-deb	0.11MB	⚠️	940.89MB	940.78MB	140.00MB
datadog-agent-amd64-deb	0.10MB	⚠️	1011.52MB	1011.42MB	140.00MB
datadog-agent-x86_64-rpm	0.10MB	⚠️	1020.84MB	1020.73MB	140.00MB
datadog-agent-x86_64-suse	0.10MB	⚠️	1020.84MB	1020.73MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	58.62MB	58.62MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	58.70MB	58.70MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	58.70MB	58.70MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	56.13MB	56.13MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	506.16MB	506.16MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.81MB	113.81MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.88MB	113.88MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.88MB	113.88MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	109.25MB	109.25MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	109.32MB	109.32MB	10.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: c11c9c56-3d27-41e0-bce8-6779c5ff064d

Baseline: 44411ed
Comparison: 6f1383a
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	+0.21	[+0.15, +0.27]	1	Logs
➖	quality_gate_idle	memory utilization	+0.17	[+0.13, +0.21]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	+0.14	[-0.63, +0.92]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.06	[-0.40, +0.53]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.05	[-0.83, +0.93]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.01	[-0.70, +0.72]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.01	[-0.09, +0.10]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.00	[-0.90, +0.91]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.12, +0.12]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.00	[-0.65, +0.64]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.02, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.01	[-0.96, +0.94]	1	Logs
➖	file_tree	memory utilization	-0.16	[-0.30, -0.03]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.35	[-3.57, +2.86]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.47	[-1.25, +0.31]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.51	[-2.17, -0.85]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	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	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, 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_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[paulcacheux]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2025-01-07 21:27:24 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-01-07 21:51:48 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 37m.

---

2025-01-07 22:24:02 UTC ℹ️ MergeQueue: This merge request was merged