[Ingest Manager] Fix and improve agent status #71009
Merged
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
nchaulet
added
v8.0.0
release_note:skip
nchaulet
changed the title
|
@nchaulet looks good! My only question is when an agent has unenrolled, when does it get removed from the Fleet page? It'd be nice to have a way to clear the page of Agents that are not relevant anymore. |
|
When the agent succesfully unenroll it become
|
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
|
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
jen-huang
approved these changes
Jul 8, 2020
nchaulet
added a commit
to nchaulet/kibana
that referenced
this pull request
Jul 9, 2020
nchaulet
added a commit
that referenced
this pull request
Jul 9, 2020
This was referenced Dec 10, 2020
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.
Summary
Resolve:
API change
@michalpristas @blakerouse the checkin api will now accept a
status?: "online" | "error" | "degraded"property in the request body. If the agent set the status to error or degraded it will stay like this until you checkin with a status of onlineUI change
@hbharding @mostlyjason does this make sense?
Show a status of enrolling instead of error when the agent is enrolling and waiting for the first checkin
Online when the agent is running
Offline instead of error if the agent did not checkin recently
Degraded or Error if the agent report an error
Unenrolling when the agent is in the process of unenrolling -> inactive after
