0 Replies Latest reply on Dec 5, 2010 10:06 AM by lockstar

    Issues with 'Node down' alert in NPM 10.1 if an extra condition or supression exists

      We had the Advanced Alert 'node down' working in 10.0 with a simple suspression based on a custom node property.

      Ie a field like 'noalert'.

      When we upgraded to 10.1 this fails. No nodes will go into alert state 1 or 2 on the alert rule. Like nothing matches.

      When I use the same condition for suspression on something like High Packet Loss. It works.


      Seems related to how the 'Node Status' query is built with additional aguments.

      Has Anyone else seen this?


      I have searched the forums, and intend to log a ticket tomorrow with support on this.