6 Replies Latest reply on Jul 18, 2013 6:26 PM by Leon Adato

    (EDIT- it was caused by a bug, the NONE condition group doesn't work with more than 1 argument)Can't figure out why this trigger condition is not working properly...

    tmart

      This alert is supposed to alert when a node goes down as long as it doesn't contain certain things in it's node name, but it is alerting even when the node name contains these things.

       

       

      Here is what it looks like:

       

       

      Trigger alert when ALL of the following apply:

           Node status is equal to down

           Trigger alert when NONE of the following apply

                Node name contains "abcd"

                Node name contains "efgh"

       

       

       

      In the trigger actions I have it email me with the variable ${NodeName}, when I enable the alert I get alerts for servers with node names such as "abcd-server-2" and "efgh-system-h".  The body of the email will confirm that the node name contains "abcd" and "efgh" with the ${NodeName} variable.   To make it even stranger, I have an identical alert that says "trigger alert when ANY of the following apply" in the 2nd condition group and it works just perfectly(basically those alerts go to email group one, and all node down alerts that don't go to group one will go to email group two.)

        • Re: Can't figure out why this trigger condition is not working properly...
          Leon Adato

          Try changing the "NONE" option to "NOT ANY".

           

          (I believe) NONE is the equivalent of ANY, and NOT ANY is the same as ALL. In the negative, of course.

          • Re: Can't figure out why this trigger condition is not working properly...
            tmart

            So after a bunch of troubleshooting I have the alert working now, but the way I had to get it to work is not very encouraging.

             

            I have determined that when you use "trigger the alert if NONE of these conditions exist", you cannot use more than 1 argument within that condition group or it will ignore the entire group.   I figured this out by removing all but 1 condition in the "NONE" condition group.    So to make my alert work I had to force  the "NONE" group to only have 1 argument by turning it into an "ANY" inside of a "NONE".  Here's what it looks like now:

             

            Trigger alert when ALL of the following apply:

                 Node status is equal to down

                 Trigger alert when NONE of the following apply:

                     Trigger alert when ANY of the following apply:

                            Node name contains "abcd"  

                            Node name contains "efgh"

             

             

             

            I'm glad to have it working, but there is obviously a bug here.  This bug is easy to reproduce, try it for yourself:  Create a new alert that alerts when NONE of the following apply:  node status = UP, node status = DOWN.    This should send an alert out only when a node is neither up nor down, but when you enable it it will alert on every single node in your environment that is up or down.