Ad Widget

Collapse

Active agent triggers repeated actions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wilson.waters
    Junior Member
    • Dec 2012
    • 15

    #1

    Active agent triggers repeated actions

    Hi all,
    I have an issue with triggers on active agents causing multiple emails to be sent with the same message every hour. Is there a problem with my zabbix configuration or should I expect to get multiple identical notifications until the cause is resolved?

    I do not have the issue with passive agents. If a trigger is reached I get a single notification and then one more when the problem is resolved.

    I also attempted to create an action operation condition of 'Event acknowledged = "Not Ack"' for the email sending action though it doesn't solve the problem even after ack-ing the trigger on the dashboard. In fact the trigger comes back with an unacknowledged state. It's as if the original trigger is being resolved, but instantly replaced by another identical trigger perhaps?
  • neogan
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2011
    • 118

    #2
    Hi,

    Could you attach the screenshot of one trigger?

    How many problem triggers do you have?

    Comment

    • wilson.waters
      Junior Member
      • Dec 2012
      • 15

      #3
      Trigger definition is attached.

      So far the problem triggers seem to be ones created from discovery rules. I've created a standard trigger to test if the problem still occurs.

      Cheers,
      Wilson.
      Attached Files

      Comment

      • neogan
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Sep 2011
        • 118

        #4
        Fresh article.
        I hope it help you.

        BTW: What Conditions in your action for that trigger?

        Comment

        • wilson.waters
          Junior Member
          • Dec 2012
          • 15

          #5
          It's flappin' broken!
          Thanks, I'll give that a try.

          Action conditions are attached.
          Attached Files

          Comment

          • wilson.waters
            Junior Member
            • Dec 2012
            • 15

            #6
            I changed the trigger expression to use the {TRIGGER.VALUE} macro but it doesn't make a difference.

            Code:
            ({TRIGGER.VALUE}=0 & {Template OS Windows active:vfs.fs.size[{#FSNAME},pfree].last(0)}<10) 
            |
            ({TRIGGER.VALUE}=1 & {Template OS Windows active:vfs.fs.size[{#FSNAME},pfree].last(0)}<10.5)
            I have found however that the issue only shows with triggers generated by discovery rules. Could it be that the trigger is being "rediscovered" every hour and resetting the trigger? I am getting the notifications every hour which corresponds to the discovery rule update interval.

            Thanks.

            Comment

            • wilson.waters
              Junior Member
              • Dec 2012
              • 15

              #7
              I can also confirm that if I change the update interval for the discovery rule to 5 minutes the notifications also get sent every 5 minutes.

              Comment

              • Linwood
                Senior Member
                • Dec 2013
                • 398

                #8
                Mail from discovery actions repeat -- not triggers - solution?

                <<< Ignore please - posted in error>>>>>
                Last edited by Linwood; 07-01-2014, 01:16. Reason: Can't find a "delete"

                Comment

                • wilson.waters
                  Junior Member
                  • Dec 2012
                  • 15

                  #9
                  Solved

                  For anyone interested. I found why triggers were being repeated for discovered items on our server.

                  One of our templates had an item duplicated in both the standard items and discovery item prototypes. In our case it was
                  vfs.fs.size[{#FSNAME},pfree] (in discovery items)
                  vfs.fs.size[{C:},pfree] (in standard items)

                  Delete the standard item and now we only get a single trigger per fault.

                  I only found it when solving another (bigger!) problem that drives other than c: weren't being discovered with this template.

                  Comment

                  Working...