WORKAROUND:
1. Please go to Administration | Agents | Agent Managers and click on "Disconnected Agent Managers" and delete the desired Agent Manager.
2. Another option: Please refer to the attached document
- How to fully removed a host (FglAM, agents, all history, data) from Foglight
For this one, follow the document provided.
- How to retire/decommission a host to keep the historical data but, no alarms/events should be triggered
Just delete the FglAM component.
NOTE: If the Host object has already been removed, it's possible to begin getting alerts from the rule "Remote Agent Managers State Per Host". This usually indicates a FglAM is down or stopped on the client (even if the FglAM has been from the client). In this case remove the RemoteClient topology as described in the attached doc and look for the FglAM that is alerting.
Foglight Agent Manager (FglAM) clients removed from the Data Management dashboard do not remove the associated FglClientInstance & RemoteClient topology objects.
WORKAROUND:
1. Please go to Administration | Agents | Agent Managers and click on "Disconnected Agent Managers" and delete the desired Agent Manager.
2. Another option: Please refer to the attached document
- How to fully removed a host (FglAM, agents, all history, data) from Foglight
For this one, follow the document provided.
- How to retire/decommission a host to keep the historical data but, no alarms/events should be triggered
Just delete the FglAM component.
NOTE: If the Host object has already been removed, it's possible to begin getting alerts from the rule "Remote Agent Managers State Per Host". This usually indicates a FglAM is down or stopped on the client (even if the FglAM has been from the client). In this case remove the RemoteClient topology as described in the attached doc and look for the FglAM that is alerting.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center