With the work @michel-laterman has done for https://github.com/elastic/elastic-agent/issues/484, Agent will send Fleet Server a reason for uninstalling when it is uninstalled. In the future, Endpoint will do the same. These components do this by calling the POST /api/fleet/agents/:id/audit/unenroll Fleet Server API. Note that this is a best effort API call.
We should surface this reason in the Fleet UI, which would be an improvement over what happens today when an Agent is uninstalled: the Agent leaves "offline" entries in the UI.
Describe a specific use case for the feature:
Clarifying the Agent listing in the Fleet UI by distinguishing between Agents that are active but currently offline with Agents that have been uninstalled.
Describe the feature:
With the work @michel-laterman has done for https://github.com/elastic/elastic-agent/issues/484, Agent will send Fleet Server a reason for uninstalling when it is uninstalled. In the future, Endpoint will do the same. These components do this by calling the
POST /api/fleet/agents/:id/audit/unenroll
Fleet Server API. Note that this is a best effort API call.We should surface this reason in the Fleet UI, which would be an improvement over what happens today when an Agent is uninstalled: the Agent leaves "offline" entries in the UI.
Describe a specific use case for the feature:
Clarifying the Agent listing in the Fleet UI by distinguishing between Agents that are active but currently offline with Agents that have been uninstalled.