Update the list of statuses for Elastic Agent #2875
Merged
+4
−0
Conversation
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
🔍 Preview links for changed docs |
vishaangelova
force-pushed
the
2333-update-agent-statuses
branch
from
3ba78ae to
b552259
Compare
vishaangelova
force-pushed
the
2333-update-agent-statuses
branch
from
b552259 to
a174fef
Compare
cmacknz
approved these changes
Sep 10, 2025
karenzone
approved these changes
Sep 10, 2025
| | --- | --- | | ||
| | **Healthy** | {{agent}}s are enrolled and checked in. There are no agent policy updates or automatic agent binary updates in progress, but the agent binary may still be out of date. {{agent}}s continuously check in to the {{fleet-server}} for required updates. | | ||
| | **Unhealthy** | {{agent}}s have errors or are running in a degraded state. An agent will be reported as `unhealthy` as a result of a configuration problem on the host system. For example, an {{agent}} may not have the correct permissions required to run an integration that has been added to the {{agent}} policy. In this case, you may need to investigate and address the situation. | | ||
| | **Orphaned** | For {{agent}}s enrolled in {{elastic-defend}}, the `orphaned` status indicates an error in the communication between the {{agent}} service on the host system and the endpoint security service provided by {{elastic-defend}}. Note that on agents reported as `orphaned`, the {{elastic-defend}} integration is still running and protecting the host. | |
There was a problem hiding this comment.
Suggested change
| | **Orphaned** | For {{agent}}s enrolled in {{elastic-defend}}, the `orphaned` status indicates an error in the communication between the {{agent}} service on the host system and the endpoint security service provided by {{elastic-defend}}. Note that on agents reported as `orphaned`, the {{elastic-defend}} integration is still running and protecting the host. | | |
| | **Orphaned** | For {{agent}}s enrolled in {{elastic-defend}}, the `orphaned` status indicates an error in the communication between the {{agent}} service on the host system and the endpoint security service provided by {{elastic-defend}}. Note that the {{elastic-defend}} integration is still running and protecting the host even on agents that are reported as `orphaned`. | |
Endpoint and Fleet gained the ability to report the orphaned status in 8.16.0 via https://github.com/elastic/endpoint-dev/commit/72e3a9b607b71e1bb2b475f2ce16397e4621a9dc and elastic/fleet-server@b8f864b |
|
Thanks, Craig. We agreed not to add the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This PR adds the
OrphanedandUninstalledstatuses to the list of statuses in the Monitor Elastic Agents doc, and updates the diagram showing the flow of Elastic Agent statuses.Closes #2333