-
Notifications
You must be signed in to change notification settings - Fork 154
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.17](backport #6068) re-enable otel subcommand on Windows #6628
Conversation
* move processing windows events earlier in the boot process * add Windows to otel integration tests (cherry picked from commit 8e83ce0)
@andrzej-stencel Not sure the lint error should be a blocker in this case. Thoughts? |
I think this change might depend on #5767, which hasn't been backported to 8.17. @leehinman do you remember? |
Tried to automatically create a backport for #6629 but looks like there are a lot of conflicts 😢 |
It does depend on #5767. Not sure why that wasn't backported. @blakerouse do you happen to remember? |
|
I'll close this PR without merging, as we're not eager to have this in 8.17. This should go into 8.18. |
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
This is an automatic backport of pull request #6068 done by [Mergify](https://mergify.com).