-
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
re-enable otel subcommand on Windows #6068
Conversation
This pull request does not have a backport label. Could you fix it @leehinman? 🙏
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
5b13070
to
e6091b9
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
a922b9f
to
42ed9c8
Compare
This reverts commit 43bbd46.
42ed9c8
to
d006214
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codewise looks good, tests are passing so I assume the changes did fix the issue. I guess worst case scenario is that this starts flakying on CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice optimisation, thanks for that @leehinman
@@ -154,6 +142,18 @@ func run(override cfgOverrider, testingMode bool, fleetInitTimeout time.Duration | |||
defer cancel() | |||
go service.ProcessWindowsControlEvents(stopBeat) | |||
|
|||
if err := handleUpgrade(); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
* move processing windows events earlier in the boot process * add Windows to otel integration tests (cherry picked from commit 8e83ce0)
* move processing windows events earlier in the boot process * add Windows to otel integration tests (cherry picked from commit 8e83ce0) Co-authored-by: Lee E Hinman <[email protected]> Co-authored-by: Pierre HILBERT <[email protected]>
What does this PR do?
Why is it important?
Previously when Windows was added,
elastic-agent
did not respond to the Windows Service manager quickly enough that it was starting and was deemed "unresponsive". Moving the go routine that responds to the Windows Service Manager earlier in the boot process should make this less likely. Given go's design of DLL loading and init code we can't eliminate this completely.Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
None.
How to test this PR locally
Related issues
Questions to ask yourself