Ad Widget

Collapse

Why no "trigger value" option in Actions condition list in version 3.2.0?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wwyhy
    Junior Member
    • Dec 2014
    • 8

    #1

    Why no "trigger value" option in Actions condition list in version 3.2.0?

    After upgraded to zabbix 3.2.0, the "trigger value" option is not in the Actions condition list.

    Normally I will set the "trigger value = Problem" to trigger email notification. but now there is no "trigger value" option in 3.2.0, so is there any new way or easier way to trigger the email notification?

    Thanks!
    Br, Wayne
  • Colttt
    Senior Member
    Zabbix Certified Specialist
    • Mar 2009
    • 878

    #2
    the documentation said its still there..
    Debian-User

    Sorry for my bad english

    Comment

    • wwyhy
      Junior Member
      • Dec 2014
      • 8

      #3
      No, I guess you are mixed the "tag value" and "trigger value".

      But I don't see the "trigger value" in that page.

      Comment

      • nick0909
        Member
        • Apr 2013
        • 73

        #4
        I just upgraded to 3.2 and don't see the Trigger Value item any more either. I guess it is just assumed, my alerts are still working.

        Comment

        • wwyhy
          Junior Member
          • Dec 2014
          • 8

          #5
          Originally posted by nick0909
          I just upgraded to 3.2 and don't see the Trigger Value item any more either. I guess it is just assumed, my alerts are still working.
          How did you set up the "Trigger Actions"?

          Before upgrade to 3.2, normally I am set the "trigger value = PROBLEM" to trigger the email notification.

          But now there is no "trigger value", so are you set the "trigger severity <> Not classified" to trigger the email notification?

          Thanks!
          Br, Wayne

          Comment

          • nick0909
            Member
            • Apr 2013
            • 73

            #6
            I don't have any simple actions that use just one rule like that, mine are all set up to alert different user groups depending on what server host group the system belongs to as well as severity of the trigger. However none of them have the condition for "trigger value = problem" after the 3.2 upgrade and they still alert, so I assume you just leave that one out?

            Comment

            • nick0909
              Member
              • Apr 2013
              • 73

              #7
              And in fact that is true, "trigger value = problem" is just assumed now, because why else would you be setting up an alert?

              I just built a simple user and an action with no conditions and they got an alert when I triggered one on a server.

              Comment

              • wwyhy
                Junior Member
                • Dec 2014
                • 8

                #8
                Originally posted by nick0909
                And in fact that is true, "trigger value = problem" is just assumed now, because why else would you be setting up an alert?

                I just built a simple user and an action with no conditions and they got an alert when I triggered one on a server.
                So I don't need to set the ""trigger severity <> Not classified"" in condition. it will still trigger email notification as default. right?

                Comment

                • nick0909
                  Member
                  • Apr 2013
                  • 73

                  #9
                  Correct, don't set anything. Leave all conditions blank and test it, you will get an alert.

                  In fact, if you set it to 'trigger value = not classified' it would only fire on a trigger that is not classified. If the trigger was High, it would not fire.

                  Comment

                  • wwyhy
                    Junior Member
                    • Dec 2014
                    • 8

                    #10
                    Originally posted by nick0909
                    Correct, don't set anything. Leave all conditions blank and test it, you will get an alert.

                    In fact, if you set it to 'trigger value = not classified' it would only fire on a trigger that is not classified. If the trigger was High, it would not fire.
                    Now it is working. thank you!

                    Comment

                    • aguiraf@gmail.com
                      Junior Member
                      • Sep 2021
                      • 3

                      #11
                      The problem I'm facing with the missing "trigger value" option in Actions condition is that I can't figure out how to NOT receive notification when a trigger returns is state OK.
                      Any help appreciated, thanks

                      Comment

                      • sumitverma
                        Junior Member
                        • Oct 2021
                        • 1

                        #12

                        I just built a simple user and an action with no conditions and they got an alert when I triggered one on a server.

                        Comment

                        Working...