[Backport 7.76.x] [CWS] Skip ssh session patcher

[dd-octo-sts]

Backport 40d1f09 from #45437.

---

What does this PR do?

Skip the SSH session patcher and add a test to illustrate the current issue.
In addition, adds the possibility to check specific fields in the json returned for ssh_session events.

Motivation

The retry mechanism could cause the agent to send no more than one event per minute if an SSH session was not properly resolved.
Previously, the event was not sent and the agent would wait one minute before sending it with the unknown type. However, this authtype would never be resolved because the session was initialized before the agent started processing events. As a result, every subsequent SSH event would wait one minute for nothing, causing a significant delay in agent events, potentially blocking all the other events.

Describe how you validated your changes

Added a test that illustrate the issue : TestSSHUserSessionBlocking
With this change, the ssh_session event is now sent with authtype set to unknown and directly sent.

Error without commenting the patcher :

        	Error:      	Received unexpected error:
        	            	All attempts fail:
        	            	#1: not found
        	            	#2: not found
        	            	#3: not found
        	            	#4: not found
        	            	#5: not found
        	            	#6: not found
        	            	#7: not found
        	            	#8: not found
        	            	#9: not found
        	            	#10: not found
        	            	#11: not found
        	            	#12: not found
        	            	#13: not found
        	            	#14: not found
        	            	#15: not found
        	            	#16: not found
        	            	#17: not found
        	            	#18: not found
        	            	#19: not found
        	            	#20: not found
        	            	#21: not found
        	            	#22: not found
        	            	#23: not found
        	            	#24: not found
        	            	#25: not found
        	            	#26: not found
        	            	#27: not found
        	            	#28: not found
        	            	#29: not found
        	            	#30: not found
        	Test:       	TestSSHUserSessionBlocking/second_ssh_no_auth

[agent-platform-auto-pr]

Static quality checks

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

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	753.526 MiB
✅	agent_deb_amd64_fips	702.199 MiB
✅	agent_heroku_amd64	326.973 MiB
✅	agent_msi	663.081 MiB
✅	agent_rpm_amd64	753.510 MiB
✅	agent_rpm_amd64_fips	702.183 MiB
✅	agent_rpm_arm64	732.275 MiB
✅	agent_rpm_arm64_fips	684.262 MiB
✅	agent_suse_amd64	753.510 MiB
✅	agent_suse_amd64_fips	702.183 MiB
✅	agent_suse_arm64	732.275 MiB
✅	agent_suse_arm64_fips	684.262 MiB
✅	docker_agent_amd64	815.631 MiB
✅	docker_agent_arm64	818.983 MiB
✅	docker_agent_jmx_amd64	1006.510 MiB
✅	docker_agent_jmx_arm64	998.581 MiB
✅	docker_cluster_agent_amd64	181.088 MiB
✅	docker_cluster_agent_arm64	196.918 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.855 MiB
✅	docker_dogstatsd_arm64	37.128 MiB
✅	dogstatsd_deb_amd64	30.074 MiB
✅	dogstatsd_deb_arm64	28.219 MiB
✅	dogstatsd_rpm_amd64	30.074 MiB
✅	dogstatsd_suse_amd64	30.074 MiB
✅	iot_agent_deb_amd64	43.033 MiB
✅	iot_agent_deb_arm64	40.135 MiB
✅	iot_agent_deb_armhf	40.705 MiB
✅	iot_agent_rpm_amd64	43.034 MiB
✅	iot_agent_suse_amd64	43.034 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-17.81 KiB (0.01% reduction)	183.936 → 183.918 → 184.810
✅	agent_deb_amd64_fips	-40.09 KiB (0.02% reduction)	172.712 → 172.673 → 173.790
✅	agent_heroku_amd64	-4.23 KiB (0.00% reduction)	87.155 → 87.151 → 88.450
✅	agent_msi	-16.0 KiB (0.01% reduction)	143.168 → 143.152 → 143.300
✅	agent_rpm_amd64	+57.0 KiB (0.03% increase)	186.772 → 186.828 → 188.160
✅	agent_rpm_amd64_fips	neutral	175.791 MiB → 176.600
✅	agent_rpm_arm64	+45.25 KiB (0.03% increase)	168.642 → 168.686 → 169.930
✅	agent_rpm_arm64_fips	-36.43 KiB (0.02% reduction)	159.277 → 159.241 → 160.550
✅	agent_suse_amd64	+57.0 KiB (0.03% increase)	186.772 → 186.828 → 188.160
✅	agent_suse_amd64_fips	neutral	175.791 MiB → 176.600
✅	agent_suse_arm64	+45.25 KiB (0.03% increase)	168.642 → 168.686 → 169.930
✅	agent_suse_arm64_fips	-36.43 KiB (0.02% reduction)	159.277 → 159.241 → 160.550
✅	docker_agent_amd64	neutral	276.726 MiB → 277.400
✅	docker_agent_arm64	+2.01 KiB (0.00% increase)	264.169 → 264.171 → 266.040
✅	docker_agent_jmx_amd64	neutral	345.361 MiB → 346.020
✅	docker_agent_jmx_arm64	-5.48 KiB (0.00% reduction)	328.792 → 328.787 → 330.660
✅	docker_cluster_agent_amd64	neutral	63.991 MiB → 64.490
✅	docker_cluster_agent_arm64	neutral	60.252 MiB → 61.170
✅	docker_cws_instrumentation_amd64	neutral	2.994 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	15.036 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.361 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.950 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.828 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.961 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.961 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.291 MiB → 12.040
✅	iot_agent_deb_arm64	+2.07 KiB (0.02% increase)	9.651 → 9.653 → 10.450
✅	iot_agent_deb_armhf	neutral	9.847 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.309 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.309 MiB → 12.060

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 2f729271-eced-4119-8c25-7b9d46e6a881

Baseline: e2b2d52
Comparison: 13fb7a7
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	-4.47	[-7.47, -1.48]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.93	[+0.41, +3.46]	1	Logs bounds checks dashboard
➖	ddot_logs	memory utilization	+0.46	[+0.38, +0.53]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.41	[+0.26, +0.57]	1	Logs
➖	ddot_metrics	memory utilization	+0.23	[+0.02, +0.44]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.20	[+0.17, +0.24]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	+0.19	[+0.14, +0.24]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.15	[-0.01, +0.30]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.13	[-0.10, +0.36]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.13	[-0.07, +0.33]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.06	[-0.35, +0.47]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.05	[-0.48, +0.57]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.03	[-0.36, +0.41]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.11, +0.15]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.01	[-0.10, +0.08]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.01	[-0.14, +0.11]	1	Logs
➖	quality_gate_idle	memory utilization	-0.03	[-0.08, +0.01]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.04	[-0.10, +0.02]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.08	[-0.13, -0.04]	1	Logs
➖	docker_containers_memory	memory utilization	-0.13	[-0.21, -0.06]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.48	[-0.58, -0.37]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.58	[-0.80, -0.36]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	-1.17	[-1.25, -1.09]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-4.47	[-7.47, -1.48]	1	Logs

Bounds Checks: ❌ Failed

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	9/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 (ddprof)

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

Experiment	Variant	Replicates	Failure	Debug Dashboard
docker_containers_memory	comparison	10	Crashed (exit code: 0)	Debug Dashboard

CI Pass/Fail Decision

❌ Failed. Some Quality Gates were violated.

• 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: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
• 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 lost_bytes: 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 memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 2caad4db-db73-4706-b80b-ea6a21db3716

Baseline: e2b2d52
Comparison: 13fb7a7
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.85	[-3.91, +2.20]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	ddot_metrics	memory utilization	+0.86	[+0.64, +1.07]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.75	[-0.75, +2.26]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	+0.45	[+0.39, +0.50]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	+0.34	[+0.19, +0.50]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.10	[+0.05, +0.16]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.07	[-0.31, +0.45]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.11, +0.13]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.01	[-0.11, +0.13]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.01	[-0.08, +0.09]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.02	[-0.52, +0.49]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.03	[-0.07, +0.01]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.05	[-0.46, +0.36]	1	Logs
➖	quality_gate_idle	memory utilization	-0.11	[-0.15, -0.07]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.12	[-0.15, -0.08]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.16	[-0.39, +0.07]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.28	[-0.44, -0.13]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.32	[-0.42, -0.22]	1	Logs
➖	docker_containers_memory	memory utilization	-0.32	[-0.39, -0.25]	1	Logs
➖	ddot_logs	memory utilization	-0.35	[-0.43, -0.28]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.56	[-0.63, -0.50]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.63	[-0.85, -0.42]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_delta	memory utilization	-0.64	[-0.83, -0.44]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-0.85	[-3.91, +2.20]	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".

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

[avonengel]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-01-28 06:54:25 UTC ℹ️ Start processing command /merge

---

2026-01-28 06:54:29 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in 7.76.x is approximately 1h (p90).

---

2026-01-28 07:53:25 UTC ℹ️ MergeQueue: This merge request was merged