[9.2] (backport #11234) [otelmanager] emit starting state in the beginning #11337
Merged
VihasMakwana merged 3 commits into9.2from Nov 24, 2025
Merged
[9.2] (backport #11234) [otelmanager] emit starting state in the beginning #11337VihasMakwana merged 3 commits into9.2from
VihasMakwana merged 3 commits into9.2from
Conversation
* feat: emit starting state * test * rename method * emit starting state * fix test * comments * fix case * ut (cherry picked from commit 14c87c2)
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
VihasMakwana
previously approved these changes
Nov 21, 2025
VihasMakwana
approved these changes
Nov 21, 2025
Contributor
Author
|
This pull request has not been merged yet. Could you please review and merge it @VihasMakwana? 🙏 |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsHistory
|
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
2 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?
This PR introduces support for emitting a STARTING state when the collector is expect the collector to start.
Why is it important?
Right now, we default to a
STOPPEDstate whenever an error occurs while accessing the healthcheck port. As a result, theelastic-agent statusoutput does not show any monitoring components. If this error occurs consistently every time the collector starts, those components will never appear inelastic-agent status.Checklist
./changelog/fragmentsusing the changelog toolHow to test this PR locally
For mac,
Startingstate, thenFailedstate with messageOTel manager failed ... process exited with status 1.Related issues
This is an automatic backport of pull request #11234 done by [Mergify](https://mergify.com).