chore(origindetection): remove OriginInfo.PodUID field

[wdhif]

What does this PR do?

Removes the OriginInfo.PodUID in favor of OriginInfo.LocalData.PodUID.

Motivation

This is done to allow for migration from taggertypes to origindetection.

Describe how you validated your changes

QA done by unit and E2E tests.

Possible Drawbacks / Trade-offs

None

Additional Notes

N/A

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 2141b038735ed4f0e75fb68917c455754923c94e

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	1009.52MB	1009.52MB	0.50MB
datadog-agent-x86_64-rpm	0.00MB	✅	1018.84MB	1018.84MB	0.50MB
datadog-agent-x86_64-suse	0.00MB	✅	1018.84MB	1018.84MB	0.50MB
datadog-agent-arm64-deb	0.00MB	✅	939.28MB	939.28MB	0.50MB
datadog-agent-aarch64-rpm	0.00MB	✅	948.58MB	948.58MB	0.50MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	56.33MB	56.33MB	0.50MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	506.82MB	506.82MB	0.50MB
datadog-dogstatsd-x86_64-rpm	-0.00MB	✅	58.90MB	58.90MB	0.50MB
datadog-dogstatsd-x86_64-suse	-0.00MB	✅	58.90MB	58.90MB	0.50MB
datadog-iot-agent-aarch64-rpm	-0.00MB	✅	109.69MB	109.69MB	0.50MB
datadog-dogstatsd-amd64-deb	-0.00MB	✅	58.83MB	58.83MB	0.50MB
datadog-iot-agent-arm64-deb	-0.00MB	✅	109.62MB	109.63MB	0.50MB
datadog-iot-agent-amd64-deb	-0.00MB	✅	114.20MB	114.20MB	0.50MB
datadog-iot-agent-x86_64-rpm	-0.00MB	✅	114.27MB	114.27MB	0.50MB
datadog-iot-agent-x86_64-suse	-0.00MB	✅	114.26MB	114.27MB	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=52695685 --os-family=ubuntu

Note: This applies to commit e5bbaeb

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 39143c72-9c19-498d-8ce1-e40310a8c5fc

Baseline: 093a1fb
Comparison: e5bbaeb
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+4.63	[+1.39, +7.86]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+1.46	[+1.39, +1.52]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.31	[-0.15, +0.77]	1	Logs
➖	file_tree	memory utilization	+0.23	[+0.09, +0.36]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.20	[+0.11, +0.28]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	+0.15	[-0.63, +0.94]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.07	[-0.62, +0.76]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.03	[-0.90, +0.96]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.11, +0.08]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.02	[-0.93, +0.90]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.03	[-0.92, +0.86]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.03	[-0.67, +0.60]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.27	[-1.06, +0.52]	1	Logs
➖	quality_gate_idle	memory utilization	-0.47	[-0.50, -0.43]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.74	[-1.45, -0.03]	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_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, 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.

[gabedos]

Looks good on the tagger side

[wdhif]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2025-01-13 20:51:09 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 35m.

---

2025-01-13 21:24:28 UTC ℹ️ MergeQueue: This merge request was merged