[beatreceiver] add remaining inputs for our test use cases

[leehinman]

What does this PR do?

Adds the Filebeat log, journald and winlog inputs. Also adds the Metricbeat kubernetes and linux metrics.

Why is it important?

Needed to test the otel runtime with the integrations and operating systems in our test cases.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Test system integration with _runtime_experimental set to otel for all inputs on Windows or Kubernetes integration with _runtime_experimental set to otel for all inputs.

Related issues

• Relates [beat_receiver] Add missing inputs for filebeatreceiver and metricbeatreceiver #9057

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @leehinman? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports 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.

[swiatekm]

Do all of these actually work? It would be good to have a unit or integration test confirming the otel collector actually starts with these enabled.

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[leehinman]

Do all of these actually work? It would be good to have a unit or integration test confirming the otel collector actually starts with these enabled.

Tested by hand on Linux & Windows. We could add integration tests but I don't think we want elastic-agent repo to have a massive test suite checking every filebeat input and metricbeat input we add. I think it is better if we put effort towards elastic/elastic-package#2975 so we can do that kind of testing in the integrations repo.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: fa2eabb

History

• 💛 Build #29280 was flaky 629fc42

cc @leehinman