chore: Update Security Filter Initialization

[gabedos]

What does this PR do?

Updates the new filter config introduced in #44258 to properly reference the pause container configuration option.

exclude_pause_containers => exclude_pause_container

Describe how you validated your changes

Unit tests

Additional Notes

No user impact. These filters have been defined to be lazily loaded but they are currently used no where.

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 59c4a3e
📊 Static Quality Gates Dashboard

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-17.4 KiB (0.00% reduction)	705.290 → 705.273 → 708.410
✅	agent_deb_amd64_fips	-17.4 KiB (0.00% reduction)	700.567 → 700.550 → 704.000
✅	agent_heroku_amd64	-17.4 KiB (0.01% reduction)	326.933 → 326.916 → 329.530
✅	agent_msi	-10.49 KiB (0.00% reduction)	571.545 → 571.534 → 982.080
✅	agent_rpm_amd64	-17.4 KiB (0.00% reduction)	705.276 → 705.259 → 708.380
✅	agent_rpm_amd64_fips	-17.4 KiB (0.00% reduction)	700.554 → 700.537 → 703.990
✅	agent_suse_amd64	-17.4 KiB (0.00% reduction)	705.276 → 705.259 → 708.380
✅	agent_suse_amd64_fips	-17.4 KiB (0.00% reduction)	700.554 → 700.537 → 703.990
✅	docker_agent_amd64	-17.39 KiB (0.00% reduction)	767.485 → 767.468 → 770.720
✅	docker_agent_jmx_amd64	-17.4 KiB (0.00% reduction)	958.364 → 958.347 → 961.600

21 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_rpm_arm64	686.832 MiB
✅	agent_rpm_arm64_fips	682.938 MiB
✅	agent_suse_arm64	686.832 MiB
✅	agent_suse_arm64_fips	682.938 MiB
✅	docker_agent_arm64	773.619 MiB
✅	docker_agent_jmx_arm64	953.217 MiB
✅	docker_cluster_agent_amd64	180.715 MiB
✅	docker_cluster_agent_arm64	196.557 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.808 MiB
✅	docker_dogstatsd_arm64	37.128 MiB
✅	dogstatsd_deb_amd64	30.027 MiB
✅	dogstatsd_deb_arm64	28.176 MiB
✅	dogstatsd_rpm_amd64	30.027 MiB
✅	dogstatsd_suse_amd64	30.027 MiB
✅	iot_agent_deb_amd64	42.987 MiB
✅	iot_agent_deb_arm64	40.112 MiB
✅	iot_agent_deb_armhf	40.689 MiB
✅	iot_agent_rpm_amd64	42.987 MiB
✅	iot_agent_suse_amd64	42.987 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+68.37 KiB (0.04% increase)	173.284 → 173.350 → 174.490
✅	agent_deb_amd64_fips	+49.86 KiB (0.03% increase)	172.210 → 172.259 → 173.750
✅	agent_heroku_amd64	+3.62 KiB (0.00% increase)	87.113 → 87.116 → 88.450
✅	agent_msi	neutral	142.930 MiB
✅	agent_rpm_amd64	-25.77 KiB (0.01% reduction)	176.160 → 176.135 → 177.660
✅	agent_rpm_amd64_fips	-32.03 KiB (0.02% reduction)	174.976 → 174.945 → 176.600
✅	agent_rpm_arm64	-23.27 KiB (0.01% reduction)	159.341 → 159.319 → 161.260
✅	agent_rpm_arm64_fips	-36.74 KiB (0.02% reduction)	158.773 → 158.737 → 160.550
✅	agent_suse_amd64	-25.77 KiB (0.01% reduction)	176.160 → 176.135 → 177.660
✅	agent_suse_amd64_fips	-32.03 KiB (0.02% reduction)	174.976 → 174.945 → 176.600
✅	agent_suse_arm64	-23.27 KiB (0.01% reduction)	159.341 → 159.319 → 161.260
✅	agent_suse_arm64_fips	-36.74 KiB (0.02% reduction)	158.773 → 158.737 → 160.550
✅	docker_agent_amd64	-21.56 KiB (0.01% reduction)	261.048 → 261.027 → 262.450
✅	docker_agent_arm64	+4.83 KiB (0.00% increase)	250.048 → 250.053 → 252.630
✅	docker_agent_jmx_amd64	-7.34 KiB (0.00% reduction)	329.678 → 329.671 → 331.080
✅	docker_agent_jmx_arm64	+17.81 KiB (0.01% increase)	314.667 → 314.684 → 317.270
✅	docker_cluster_agent_amd64	neutral	63.835 MiB
✅	docker_cluster_agent_arm64	neutral	60.121 MiB
✅	docker_cws_instrumentation_amd64	neutral	2.994 MiB
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB
✅	docker_dogstatsd_amd64	neutral	15.026 MiB
✅	docker_dogstatsd_arm64	neutral	14.355 MiB
✅	dogstatsd_deb_amd64	neutral	7.944 MiB
✅	dogstatsd_deb_arm64	neutral	6.824 MiB
✅	dogstatsd_rpm_amd64	neutral	7.956 MiB
✅	dogstatsd_suse_amd64	neutral	7.956 MiB
✅	iot_agent_deb_amd64	+2.6 KiB (0.02% increase)	11.257 → 11.260 → 12.040
✅	iot_agent_deb_arm64	+2.84 KiB (0.03% increase)	9.631 → 9.634 → 10.450
✅	iot_agent_deb_armhf	-3.09 KiB (0.03% reduction)	9.826 → 9.823 → 10.620
✅	iot_agent_rpm_amd64	+2.21 KiB (0.02% increase)	11.276 → 11.279 → 12.060
✅	iot_agent_suse_amd64	+2.21 KiB (0.02% increase)	11.276 → 11.279 → 12.060

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: a656fad6-3399-413b-b509-27ed823030f4

Baseline: 59c4a3e
Comparison: d13ee63
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	-0.30	[-3.22, +2.62]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.08	[-0.40, +2.56]	1	Logs bounds checks dashboard
➖	ddot_metrics	memory utilization	+0.68	[+0.46, +0.91]	1	Logs
➖	file_tree	memory utilization	+0.20	[+0.14, +0.26]	1	Logs
➖	quality_gate_idle	memory utilization	+0.15	[+0.10, +0.19]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.13	[+0.07, +0.18]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.11	[+0.07, +0.15]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	+0.00	[-0.38, +0.39]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.09, +0.09]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.00	[-0.05, +0.05]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.00	[-0.13, +0.12]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.01	[-0.51, +0.49]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.15, +0.12]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.03	[-0.44, +0.39]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.07	[-0.30, +0.16]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.13	[-0.29, +0.02]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.28	[-0.48, -0.07]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.28	[-0.43, -0.12]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-0.30	[-3.22, +2.62]	1	Logs
➖	ddot_logs	memory utilization	-0.33	[-0.40, -0.27]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.38	[-0.59, -0.17]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	-0.53	[-0.62, -0.44]	1	Logs
➖	docker_containers_memory	memory utilization	-0.67	[-0.74, -0.60]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.62	[-1.70, -1.54]	1	Logs

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	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	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:

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

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Profiling Replicate Execution Failures (target internal profiling)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle_all_features	baseline	11 (x3)	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	11 (x4)	Oom killed	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 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_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_logs, bounds check intake_connections: 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: 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.

[gabedos]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-01-15 16:45:10 UTC ℹ️ Start processing command /merge

---

2026-01-15 16:45:55 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
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.

---

2026-01-15 19:51:43 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 60m (p90).

---

2026-01-15 20:31:59 UTC ℹ️ MergeQueue: This merge request was merged