[OTEL-2125] Add E2E test for no dd exporter case

[songy23]

What does this PR do?

Add an E2E test case for OTel agent with no datadog exporter config.

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

Note: This applies to commit ca211b5

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 3be3c57b-3f44-4ace-b7d7-114bd032abc5

Baseline: 919ff87
Comparison: b01007e
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	otel_to_otel_logs	ingress throughput	+0.41	[-0.27, +1.09]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.08	[-0.79, +0.96]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.03	[-0.62, +0.67]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.10, +0.14]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.01	[-0.46, +0.47]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.00	[-0.92, +0.91]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.05	[-0.82, +0.73]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.07	[-0.96, +0.83]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.13	[-0.87, +0.61]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.31	[-1.11, +0.48]	1	Logs
➖	quality_gate_idle	memory utilization	-0.52	[-0.56, -0.48]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	-0.55	[-0.69, -0.42]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.61	[-0.67, -0.55]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.81	[-0.90, -0.73]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.08	[-1.76, -0.39]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.44	[-4.62, +1.74]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	quality_gate_idle	memory_usage	9/10	bounds checks dashboard
✅	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_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

❌ Failed. Some Quality Gates were violated.

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

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor f4ae8f0fd12ff1bc2c42f54f07dc00223f492a22

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.00MB	✅	1187.90MB	1187.90MB	140.00MB
datadog-agent-x86_64-rpm	0.00MB	✅	1197.14MB	1197.14MB	140.00MB
datadog-agent-x86_64-suse	0.00MB	✅	1197.14MB	1197.14MB	140.00MB
datadog-agent-arm64-deb	0.00MB	✅	933.88MB	933.88MB	140.00MB
datadog-agent-aarch64-rpm	0.00MB	✅	943.10MB	943.10MB	140.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.59MB	78.59MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.67MB	78.67MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.67MB	78.67MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.79MB	55.79MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	505.07MB	505.07MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.31MB	113.31MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.38MB	113.38MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.38MB	113.38MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.78MB	108.78MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	108.85MB	108.85MB	10.00MB

Decision

✅ Passed

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 51510998 (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

[songy23]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-18 21:51:51 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-18 22:37:06 UTC ⚠️ MergeQueue: This merge request was unqueued

This merge request was unqueued

[songy23]

/merge -c

[songy23]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-19 05:08:31 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.

Use /merge -c to cancel this operation!

---

⏳ Processing ...