trivy: simplify disabled collector building

[paulcacheux]

What does this PR do?

The list of enabled analyzers is short (by default ["os"], maybe in the future ["os", "languages"]). As such there is no need for a binary search that is harder to understand.

Motivation

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 38beef2b6c213d4f6a44866ece73cbcc2f36b7f2

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	928.92MB	928.92MB	0.50MB
datadog-agent-x86_64-rpm	0.00MB	✅	938.66MB	938.66MB	0.50MB
datadog-agent-x86_64-suse	0.00MB	✅	938.66MB	938.66MB	0.50MB
datadog-agent-arm64-deb	0.00MB	✅	916.09MB	916.09MB	0.50MB
datadog-agent-aarch64-rpm	0.00MB	✅	925.81MB	925.81MB	0.50MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	59.01MB	59.01MB	0.50MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	59.09MB	59.09MB	0.50MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	59.09MB	59.09MB	0.50MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	56.50MB	56.50MB	0.50MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	477.89MB	477.89MB	0.50MB
datadog-iot-agent-amd64-deb	0.00MB	✅	93.88MB	93.88MB	0.50MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	93.95MB	93.95MB	0.50MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	93.95MB	93.95MB	0.50MB
datadog-iot-agent-arm64-deb	0.00MB	✅	89.93MB	89.93MB	0.50MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	90.00MB	90.00MB	0.50MB

Decision

✅ Passed

[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=54024699 --os-family=ubuntu

Note: This applies to commit 296e1f5

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 54024699 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 7f92a361-6e31-4a21-a3a9-db53618bfec8

Baseline: 38beef2
Comparison: 296e1f5
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.23	[+2.16, +2.31]	1	Logs
➖	quality_gate_idle	memory utilization	+0.55	[+0.51, +0.59]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.46	[+0.42, +0.51]	1	Logs bounds checks dashboard
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.37	[-0.40, +1.14]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.13	[-0.79, +1.05]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.08	[-0.84, +1.00]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.04	[-0.73, +0.82]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.28, +0.29]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.03, +0.02]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.01	[-0.85, +0.83]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.01	[-0.48, +0.46]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.01	[-0.65, +0.62]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.02	[-0.73, +0.70]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.08	[-0.99, +0.84]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.15	[-3.20, +2.90]	1	Logs
➖	file_tree	memory utilization	-0.22	[-0.28, -0.17]	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	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
✅	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_idle_all_features, 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, 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 intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.

[paulcacheux]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2025-02-10 13:42:51 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 29m.

---

2025-02-10 14:16:27 UTC ℹ️ MergeQueue: This merge request was merged