[beatreceiver] Add e2e tests for tcp and udp inputs

[khushijain21]

Proposed commit message

This PR adds e2e test that compares document ingested by tcp and udp input in standalone and otel mode.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

None

How to test this PR locally

cd x-pack/filebeat
go test -run TestTCPInputOTelE2E -tags integration ./tests/integration -v 

Related issues

• Partialfix for https://github.com/elastic/ingest-dev/issues/4889

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @khushijain21? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds a new integration test file for Filebeat, otel_tcp_udp_test.go, containing two exported tests (TestTCPInputOTelE2E, TestUDPInputOTelE2E) that verify end-to-end behavior when Filebeat's TCP/UDP net inputs are routed through Elastic's OTEL pipeline. The tests generate OTEL and Filebeat configs from templates, start both the OTEL collector and Filebeat, send identical test messages via both paths, query Elasticsearch data streams for both, and assert the resulting documents match aside from a fixed set of ignored fields.

Changes

Area	Change
Integration tests	New file adding two E2E tests covering TCP and UDP input routing through OTEL, with shared setup/run helper, config generation, client execution, and Elasticsearch document comparison logic.

Suggested labels: enhancement

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@x-pack/filebeat/tests/integration/otel_tcp_udp_test.go`:
- Around line 217-226: The UDP readiness check in the otel_tcp_udp test is a
no-op because net.Dial on UDP does not confirm the receiver is bound, so update
the readiness logic in TestUDPInputOTelE2E to wait for a log message that proves
the UDP listener started. Replace the current require.EventuallyWithTf probe
around the net.Dial call with a log-based wait such as WaitLogsContainsAnyOrder,
using the existing otelAddress/inputType context to target the OTel UDP input
startup signal before launching runClient.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 0db0cd8c-ff02-46e0-9f7c-f9eaaab23a0e

📥 Commits

Reviewing files that changed from the base of the PR and between 2145bda and 0f84f7b.

⛔ Files ignored due to path filters (1)

• x-pack/filebeat/test.log is excluded by !**/*.log

📒 Files selected for processing (1)

• x-pack/filebeat/tests/integration/otel_tcp_udp_test.go

[orestisfl]

Thanks!