Added loggers for Fleet enrollment call failures #6477
+47
−11
Conversation
This file contains 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
|
This pull request does not have a backport label. Could you fix it @Rohit-code14? 🙏
|
michalpristas
added
bug
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
buildkite test this |
|
buildkite test this |
1 similar comment
|
buildkite test this |
|
@pkoutsovasilis not sure why the buildkite test is failing..shall i merge latest changes to my branch once again? And will i be able to trigger test by commenting |
|
buildkite test this |
|
pkoutsovasilis
approved these changes
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Added logger to print the status and code when enrollment call to fleet failed.
Why is it important?
As mentioned in the issue(#6287), It will be difficult to debug enrollment failures in such cases. Therefore adding the actual status code and error in logs will be helpful for debugging.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
No disruptive user impact
Related issues
Remote server failed to handle the request, will retry in a momentneeds to be better handled #6287