[ebpfless] Separate pending connection map, handle closed connections

[pimlu]

What does this PR do?

This PR separates the conns map in TCPProcessor into pendingConns and establishedConns. There is no closedConns because these are passed directly into the tracer's closeCallback.

This PR is stacked on [ebpfless] Fix the pre-existing connection tests.

Motivation

In the future, we will limit the size of these maps and having a separate limit for pendingConns is important.
Using closeCallback is important for correctness purposes also.

Describe how you validated your changes

Run TCPProcessor test suite: (all should pass)

go test -tags=linux,linux_bpf,npm,process,test ./pkg/network/tracer/connection/ebpfless

Run the ebpfless tracer test suite: (same should pass as before)

DD_LOG_LEVEL=info DD_REMOTE_CONFIGURATION_ENABLED=false TEST_EBPFLESS_OVERRIDE=true sudo -E go test -tags=linux,linux_bpf,npm,process,test ./pkg/network/tracer -v --run TestTracerSuite/eBPFless -run TestTracerSuite/eBPFless

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

Note: This applies to commit ef16359

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 29d90d395e944a518a438b98bfc2610bddfc26df

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-arm64-deb	0.00MB	⚠️	968.50MB	968.49MB	140.00MB
datadog-agent-aarch64-rpm	0.00MB	⚠️	977.71MB	977.71MB	140.00MB
datadog-agent-amd64-deb	0.00MB	✅	1232.71MB	1232.71MB	140.00MB
datadog-agent-x86_64-rpm	0.00MB	✅	1241.94MB	1241.94MB	140.00MB
datadog-agent-x86_64-suse	0.00MB	✅	1241.94MB	1241.94MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.53MB	78.53MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.61MB	78.61MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.61MB	78.61MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.75MB	55.75MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	504.96MB	504.96MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.26MB	113.26MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.33MB	113.33MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.33MB	113.33MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.72MB	108.72MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	108.79MB	108.79MB	10.00MB

Decision

⚠️ Warning

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 5ecc97c7-be7f-48d7-aa5f-4d33b73b1a72

Baseline: 29d90d3
Comparison: ef16359
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	+1.97	[+1.91, +2.03]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.68	[-0.04, +1.40]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.39	[-0.40, +1.18]	1	Logs
➖	quality_gate_idle	memory utilization	+0.34	[+0.30, +0.39]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.30	[+0.18, +0.43]	1	Logs bounds checks dashboard
➖	otel_to_otel_logs	ingress throughput	+0.28	[-0.37, +0.93]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.06	[-0.40, +0.52]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.05	[-0.83, +0.94]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.09, +0.10]	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.03	[-0.80, +0.74]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.04	[-0.95, +0.86]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.07	[-0.94, +0.81]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.08	[-0.74, +0.58]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.15	[-0.79, +0.49]	1	Logs
➖	file_tree	memory utilization	-0.45	[-0.55, -0.34]	1	Logs
➖	quality_gate_logs	% cpu utilization	-0.92	[-3.85, +2.02]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_0ms_latency_http1	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	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_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_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.

[pimlu]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-16 22:52:16 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.

---

2024-12-16 23:44:06 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in main is 30m.

---

2024-12-17 00:20:18 UTC ℹ️ MergeQueue: This merge request was merged

[agent-platform-auto-pr]

[Fast Unit Tests Report]

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

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• 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