-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[8.x](backport #5767) Add support for running EDOT inside of running Elastic Agent #6096
Conversation
(cherry picked from commit b07566b) # Conflicts: # NOTICE.txt # go.mod # go.sum
Cherry-pick of b07566b has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request has not been merged yet. Could you please review and merge it @blakerouse? 🙏 |
@mergify rebase |
☑️ Nothing to do
|
@mergify update |
☑️ Nothing to do
|
Quality Gate failedFailed conditions |
What does this PR do?
Adds the ability to run the EDOT along side the running Elastic Agent.
This connects the EDOT into the coordinator of the Elastic Agent. At any point if any of these top-level keys (
receivers
,processors
,exporters
,extensions
,service
) exist in the configuration or policy for the elastic-agent the EDOT is started. If all of those keys are removed from the configuration or policy then the EDOT is automatically stopped. If any configuration change occurs the updated configuration is passed along to the EDOT to handle.Why is it important?
This allows EDOT configuration to exist inside of the configuration or policy and allow it to work as expected.
Checklist
[ ] I have made corresponding changes to the documentation./changelog/fragments
using the changelog toolDisruptive User Impact
This is an addition and doesn't affect the way the current Elastic Agent runs at all.
How to test this PR locally
Place OTel configuration into the
elastic-agent.yml
:Run
elastic-agent run -e
.Related issues
Closes #5796
This is an automatic backport of pull request #5767 done by Mergify.