Add logsagentpipeline component for OTLP ingest paths

[liustanley]

What does this PR do?

This PR adds logs agent setup files in comp/otelcol/logsagentpipeline. This includes agent.go which mirrors the logs agent initialization files in comp/logs/agent, with only the pipeline components that are needed for OTLP ingest paths (otel-agent and collector datadog exporter).

This PR also modifies the otel-agent run subcommand to use logsagentpipeline instead of the logs agent in comp/logs/agent.

Motivation

This code was initially added to collector-contrib in this PR: open-telemetry/opentelemetry-collector-contrib#32327, but needs to be added in datadog-agent instead to be used by the otel-agent.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[gh123man]

I don't see any obvious issues with how this is set up. so LGTM 👍
Just made a couple of small suggestions.

you may also consider renaming these files to be more otel specific - up to you though.

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 6ff0dc23-18a7-4f33-a65d-23249d8f91da
Baseline: 9581bfe
Comparison: 8c8d4b3

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

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI
❌	file_to_blackhole	% cpu utilization	+15.13	[+8.96, +21.30]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
❌	file_to_blackhole	% cpu utilization	+15.13	[+8.96, +21.30]
➖	basic_py_check	% cpu utilization	+2.09	[-0.51, +4.70]
➖	idle	memory utilization	+0.32	[+0.29, +0.36]
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.19, +0.22]
➖	trace_agent_json	ingress throughput	+0.01	[-0.01, +0.02]
➖	otel_to_otel_logs	ingress throughput	-0.00	[-0.36, +0.35]
➖	trace_agent_msgpack	ingress throughput	-0.01	[-0.02, -0.00]
➖	process_agent_standard_check_with_stats	memory utilization	-0.05	[-0.10, +0.00]
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.06	[-0.10, -0.02]
➖	process_agent_real_time_mode	memory utilization	-0.24	[-0.27, -0.20]
➖	process_agent_standard_check	memory utilization	-0.25	[-0.31, -0.20]
➖	file_tree	memory utilization	-0.47	[-0.56, -0.37]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.11	[-3.90, +1.67]
➖	pycheck_1000_100byte_tags	% cpu utilization	-1.31	[-6.06, +3.45]
➖	tcp_syslog_to_blackhole	ingress throughput	-7.72	[-28.09, +12.66]

Explanation

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

[cit-pr-commenter]

Go Package Import Differences

Baseline: 9581bfe
Comparison: 8c8d4b3

binary	os	arch	change
agent	linux	amd64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
agent	linux	arm64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
agent	windows	amd64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
agent	windows	386	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
agent	darwin	amd64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
agent	darwin	arm64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
iot-agent	linux	amd64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
iot-agent	linux	arm64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline
heroku-agent	linux	amd64	+1, -0 +github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline

[pr-commenter]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=33063667 --os-family=ubuntu

[dustmop]

LGTM

[CelianR]

Lgtm for agent ci experience files 👍

[liustanley]

/merge

[dd-devflow]

🚂 MergeQueue

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!

[dd-devflow]

🚂 MergeQueue

Pull request added to the queue.

There are 6 builds ahead! (estimated merge in less than 3h)

Use /merge -c to cancel this operation!