Auto-unmanaging or Deleting Containerized Applications

Once the containerized applications are managed as components by the eG manager after being discovered by the eG agents, eG Enterprise employs agentless technique to monitor each managed component, and periodically pulls performance metrics from them. Sometimes, eG agents may stop pulling metrics from a component. The failure may persist if the target application is no longer part of the monitored infrastructure or has been shut down for regular maintenance or upgrades. Administrators would be right to delete or at least temporarily unmanage such components to save monitoring resources. This can however prove to be a challenge in large dynamic infrastructures, where components are added/removed frequently. In such environments, administrators can find it cumbersome to identify components that are no longer reporting metrics and to manually delete/unmanage them from the eG Enterprise system. To minimize the administrative effort involved in this exercise, you can now configure the eG manager to automatically unmanage/delete components that are not reporting metrics beyond a configured duration.

To achieve the above, do the following:

  1. Login to the eG admin interface.
  2. Follow the Infrastructure -> Discovery menu sequence.
  3. Select the Auto unmanage/delete option under the Containerized Applications sub-node of the Kubernetes Infrastructure sub-node in the Auto Scaling Environment sub-node of the Agent Discovery node in the discovery tree. The right panel will change to display a Containerized applications - AUTO UNMANAGE/DELETE page (see Figure 1).

    Figure 1 : Auto-unmanaging/deleting discovered containerized applications

  4. To enable the eG manager to automatically unmanage/delete the discovered containerized applications that are not reporting, turn on the Enable automatic actions on components that are not reporting flag to Yes.
  5. Next, indicate what action you want to automate on components that are not reporting. If you want to delete such components automatically, then select the Delete option from the What action would you like to take? list. If you want to unmanage the components, select the Unmanage option from the What action would you like to take? list.
  6. Then, specify when the chosen action should be triggered. In other words, in the Take action for components that are not reporting for text box, mention how long a component should not be reporting metrics for it to be auto-deleted/unmanaged by the eG manager.
  7. You may want to unmanage/delete a component that is not reporting metrics for the said duration, only if that component is of a type that has been explicitly configured to be auto-managed upon discovery. To instruct the manager so, set the Take action for component types in list to Auto-manage List. On the other hand, if you want to initiate the chosen action on a component whether/not it belongs to the 'auto-manage' list, then choose Discovery List from this list.
  8. If the Delete option is chosen from the What action would you like to take? list, then by default, eG Enterprise will automatically delete only those components that are in the unmanaged state and have not been reporting metrics for the configured duration. If you want the eG manager to auto-delete even the managed components, then set the Take action on managed components also? flag to Yes.
  9. Finally, click the Update button.