Ad Widget

Collapse

Can't disable trigger on host level

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • AlexeySaff
    Junior Member
    • Aug 2021
    • 20

    #1

    Can't disable trigger on host level

    I think starting from 7.2.1 and 7.2.2 (not sure tbh), I can't disable the trigger anymore on the host level. So let's say we have something discovered on the host from the main template, but on particular host I don't want to have specific trigger. So previously I just selected alarm and untick "enabled" on the trigger. Now in tickbox I untick and click "save" trigger and alarm is still in the list and when I go to config again tickbox is selected
  • cptneko
    Junior Member
    • Jun 2024
    • 5

    #2
    7.2.1 is definitely affected, we have noticed it too this morning. Now I upgraded to 7.2.2 in hopes of it being fixed, but still an issue for us.

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4807

      #3
      Have you checked, is there already a bug report on the topic? https://support.zabbix.com/projects/ZBX/
      If not, maybe you can submit one.

      Comment

      • thomas598brown
        Junior Member
        • Jan 2025
        • 2

        #4
        Originally posted by AlexeySaff
        I think starting from 7.2.1 and 7.2.2 (not sure tbh), I can't disable the trigger anymore on the host level. So let's say we have something discovered on the host from the main template, but on particular host I don't want to have specific trigger. So previously I just selected alarm and untick "enabled" on the trigger. Now in tickbox I untick and click "save" trigger and alarm is still in the list and when I go to config again tickbox is selected
        Hello AlexeySaff ,
        Starting from Zabbix versions 7.2.1 and 7.2.2, disabling a trigger on the host level seems to be a known issue. While previously you could simply untick "enabled" to disable a specific trigger, it no longer works consistently1. This may be something the developers are working to address, so keep an eye out for updates.

        Best Regards,
        Thomas Brown


        Comment

        • thomas598brown
          Junior Member
          • Jan 2025
          • 2

          #5
          Originally posted by thomas598brown

          Hello AlexeySaff ,
          Starting from Zabbix versions 7.2.1 and 7.2.2, disabling a trigger on the host level seems to be a known issue. While previously you could simply untick "enabled" to disable a specific trigger, it no longer works consistently. This may be something the developers are working to address, so keep an eye out for updates. WhataburgerVisit com


          Best Regards,
          Thomas Brown

          Thank You for support

          Comment

          • AlexeySaff
            Junior Member
            • Aug 2021
            • 20

            #6
            I hope that's just a temp bug and will be fixed soon. otherwise it's terrible

            Comment

            • AlexeySaff
              Junior Member
              • Aug 2021
              • 20

              #7
              https://support.zabbix.com/browse/ZBX-25857 - fingers crossed

              Comment

              • taken
                Junior Member
                • May 2015
                • 15

                #8
                They just release new 7.0.9 and problem still exist...

                Comment

                • AlexeySaff
                  Junior Member
                  • Aug 2021
                  • 20

                  #9
                  7.2.3 still the same

                  Comment

                  • AlexeySaff
                    Junior Member
                    • Aug 2021
                    • 20

                    #10
                    trigger can be disabled from the list of trigger on the host and not popup window

                    Comment

                    • AlexeySaff
                      Junior Member
                      • Aug 2021
                      • 20

                      #11
                      7.2.4 - fixed

                      Comment

                      Working...