9 Replies Latest reply on Mar 9, 2015 8:51 PM by renegadenomad x

    Trigger condition not working

    renegadenomad x

      Hi guys, I still cannot get this right. I am trying to set this particular alert to ignore all nodes with particular names (circled below), but I am still getting alerts for the nodes. I assume it is how they are indented?

       

      New JPEG image.jpg

        • Re: Trigger condition not working
          dnerdahl

          These get hard to explain because of the double and triple negatives that come into play. Hopefully I can make enough sense.

           

          Your problem is with "Trigger Alert when none of the following apply"

          The none qualifier requires that "All" of the underlying conditions be "not" true at the same time.

           

          So if a node name contains any one, or more, but not all of the phrases you've listed the node will meet your trigger criteria.

           

          An example...

          Node Name = castle

          • "Tirgger when none of the following apply"
            • Node Node contains cas (the node name "castle" contains "cas")
            • Node Name contains exc (the node name "castle doe not contain "exc")
            • Node Name contains bm (the node name "castle doe not contain "bm")
            • Node Name contains macmini (the node name "castle doe not contain "macmini")

          One of the above conditions applies to the node name and thus it will trigger for the node named "castle"

           

          ((edit: I should mention that for this alert to not trigger your nodename would have to be something like "casexcbmmacmini"))

           

          Unfortunately the 10.x Advanced Alert Manger does not have a "not like" conditional qualifier unless you want to write your own sql code. Your best bet to get this to work is to do something like this:

           

          • All
            • CPU is greater than 95
          • ANY
            • Vendor is equal to Windows
            • Vendor is equal to net-snmp
          • ANY
            • NONE
              • Node Node contains cas
            • NONE
              • Node Name contains exc
            • NONE
              • Node Name contains bm
            • NONE
              • Node Name contains macmini
          • Re: Trigger condition not working
            HolyGuacamole

            Another suggestion would be create a node custom property called AlertFlag (say) and assign Yes to the nodes you want to be alerted on. All this can be done in the web console. You alert management will be much simpler that way

             

            • All
              • CPU is greater than 95
              • AlertFlag is equal to Yes
              • Re: Trigger condition not working
                mdecima

                renegadenomad x, you should create a custom property to identify the ones you don't wish to alert, for example "Endpoints", "PCs", etc.. then in the the alert you exclude those like HolyGuacamole Suggested.

                 

                the solution would be like this.

                 

                 

                In the latest version (11.5) you could use the logic you mention, because then you could use the connector "does not contain"

                 

                *all

                CPU Load is greater than or equal to 95

                node name does not contain cas

                node name does not contain macmini

                node name does not contain exc

                node name does not contain bm

                 

                any

                 

                Vendor is equal to Windows

                Vendor is equal to net-snmp

              • Re: Trigger condition not working
                dheafey

                Hi renegadenomad x,

                 

                you can test your alerts on specific devices to see if they will fire or not.  Go here for 6.2 instructions.  In previous versions, use the procedure found here.

                • Re: Trigger condition not working
                  njoylif

                  change the None to "NOT ALL"

                  if you drop down to custom sql (copy alert if desired or cancel when done) you will see it creates:

                  ...

                  (

                     NOT (condition a) AND

                     NOT (condition b) AND

                     NOT (condition c) AND

                     NOT (condition d)

                  )

                  • Re: Trigger condition not working
                    renegadenomad x

                    Marked as correct. You guys gave great tips. Thanks!