Open for Voting
over 1 year ago

Unmanage Node

Unmanage Node should clear all active alerts against the node. Perhaps this would fix the issue where an alert condition is triggered prior to the unmanage act. Then when the node is unmanaged, it can no longer evaluate for an alert reset. Clearing the alert manually just causes it to reproduce itself even though the node is unmanaged.

Parents
  • I am pretty sure that alert reset conditions are evaluated even for unmanaged nodes.

    Un-managing a node stops all polling, and set the state to 'unmanaged' which can be used as a reset condition.

    This is somewhat implicit by many of the out of the box alerts, e.g. Node down where the set condition is 'Down' and the reset-condition is 'Not down', which also includes 'unmanaged.

Comment
  • I am pretty sure that alert reset conditions are evaluated even for unmanaged nodes.

    Un-managing a node stops all polling, and set the state to 'unmanaged' which can be used as a reset condition.

    This is somewhat implicit by many of the out of the box alerts, e.g. Node down where the set condition is 'Down' and the reset-condition is 'Not down', which also includes 'unmanaged.

Children
  • It depends on how you've configured the Alert Reset condition. I typically use the default "Reset this alert when trigger condition is no longer true (Recommended)". In doing so, if the alert trigger is on a component statistic >= 10 for example, if you are no longer collecting that metric, how would the reset condition ever be found? I don't typically use a trigger condition for a node status to not be unmanaged or a reset condition for it to be managed.