Switch to otel self-monitoring by default

[swiatekm]

What does this PR do?

Switches Elastic Agent self-monitoring to use the otel runtime by default. The self-monitoring components will run as receivers within a managed otel collector, rather than individual processes.

Why is it important?

This is the first step in an effort to give a similar treatment to all inputs. The benefit of this will be improved resource efficiency and compatibility with the otel universe.

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

There should be no user-facing impact, other than reduced resource consumption. If there is one, this change can be reversed by setting agent.monitoring._runtime_experimental: process.

How to test this PR locally

Build agent and run it with the default configuration. You should see an otel collector process, and the self-monitoring inputs should be listed in status as beats-receiver.

Related issues

• Closes [beats receivers] Enable beats receivers for internal monitoring data collection by default #9058

[mergify]

This pull request does not have a backport label. Could you fix it @swiatekm? 🙏
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.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feat/self-monitoring-otel-default-alternative upstream/feat/self-monitoring-otel-default-alternative
git merge upstream/main
git push upstream feat/self-monitoring-otel-default-alternative

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: fdfda2b

Failed CI Steps

• arm:sudo: fleet

History

• 💔 Build #29062 failed 25979bf
• 💔 Build #28999 failed 1722db1
• 💔 Build #28946 failed 7696755
• 💔 Build #28936 failed ba45fad
• 💔 Build #28887 failed ba45fad

cc @swiatekm

[elasticmachine]

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

[cmacknz]

Creating the 9.2 backport now that we are unblocked.