[9.2] (backport #10594) Switch to otel self-monitoring by default#10958
Merged
[9.2] (backport #10594) Switch to otel self-monitoring by default#10958
Conversation
* Switch to the otel runtime manager by default for self-monitoring * Update monitoring tests # Conflicts: # internal/pkg/agent/application/monitoring/component/v1_monitor_test.go * Add changelog entry (cherry picked from commit 79931dd)
mergify
bot
requested review from
pkoutsovasilis and
swiatekm
and removed request for
a team
github-actions
bot
added
enhancement
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
pierrehilbert
approved these changes
Oct 31, 2025
ebeahan
approved these changes
Oct 31, 2025
swiatekm
approved these changes
Oct 31, 2025
Contributor
💛 Build succeeded, but was flaky
Failed CI Stepscc @swiatekm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testDisruptive 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
This is an automatic backport of pull request #10594 done by [Mergify](https://mergify.com).