diff --git a/docs/management/admin/admin-pg-ov.asciidoc b/docs/management/admin/admin-pg-ov.asciidoc index 339f129651..6c1c160d7c 100644 --- a/docs/management/admin/admin-pg-ov.asciidoc +++ b/docs/management/admin/admin-pg-ov.asciidoc @@ -24,19 +24,9 @@ The Endpoints list provides the following data: * *Endpoint*: The system hostname. Click the link to display <> in a flyout. -* *Agent Status*: The current status of the {agent}, which is one of the following: - -** `Healthy`: The agent is online and communicating with {kib}. - -** `Unenrolling`: The agent is currently unenrolling and will soon be removed from Fleet. Afterward, the endpoint will also uninstall. - -** `Unhealthy`: The agent is online but requires attention from an administrator because it's reporting a problem with a process. An unhealthy status could mean an upgrade failed and was rolled back to its previous version, or an integration might be missing prerequisites or additional configuration. Refer to <> for more on resolving an unhealthy agent status. - -** `Updating`: The agent is online and is updating the agent policy or binary, or is enrolling or unenrolling. - -** `Offline`: The agent is still enrolled but may be on a machine that is shut down or currently does not have internet access. In this state, the agent is no longer communicating with {kib} at a regular interval. +* *Agent Status*: The current {fleet-guide}/monitor-elastic-agent.html#view-agent-status[status] of the {agent}. + -NOTE: {agent} statuses in {fleet} correspond to the agent statuses in the {security-app}. +NOTE: Not all {agent} statuses in {fleet} correspond to the statuses in the {security-app}. For example, an `unenrolled` {agent} in {fleet} shows as `offline` in the {security-app}. * *Policy:* The name of the associated integration policy when the agent was installed. Click the link to display the <> page.