Ad Widget

Collapse

Actions on Zabbix it's a f* mess.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • akbar415
    Senior Member
    • May 2015
    • 119

    #1

    Actions on Zabbix it's a f* mess.

    I like a lot of Zabbix, but the action configuration is a piece of shit.

    I lost one week triyng to configure it the way I want without sucess. The condition option don't work.

    I setup like this.

    Action Name: 00 - Send email Disaster/High
    Conditions:
    Code:
    A and (B or C) and (D or E)
    Label	Name	Action
    A	Maintenance status not in maintenance		
    B	Application not like OCS-Inventory		
    C	Application not like ICMP		
    D	Trigger severity >= High		
    E	Trigger severity <> Information
    Even with this configuration I'm still receiving the e-mail with trigger severity equal to Information.

    This is a bug?
  • phpclub
    Junior Member
    • Jul 2015
    • 7

    #2
    You are not making any sense in your configuration.

    (B or C) -> either its not like X OR not like Y.
    do you see sense in this? I don't. this will ALWAYS equal true.
    Because if its one, it can't be the other.

    Regarding the severity, try setting it up as one rule of => Warning

    Comment

    • akbar415
      Senior Member
      • May 2015
      • 119

      #3
      Originally posted by phpclub
      You are not making any sense in your configuration.

      (B or C) -> either its not like X OR not like Y.
      do you see sense in this? I don't. this will ALWAYS equal true.
      Because if its one, it can't be the other.
      THis is what zabbix give to me, this expression was automatically generate by zabbix, and (B or C ) it's the only part that work's. My problem is the severitty.

      Originally posted by phpclub
      Regarding the severity, try setting it up as one rule of => Warning
      I already tried the follow:

      Code:
      Trigger severity >= High (Only this)
      
      Trigger severity <> Information
      Trigger severity <> Warning
      Trigger severity <> Average
      And all combinations that I imagined withou success.

      Comment

      • eav
        Junior Member
        • Jul 2015
        • 4

        #4
        Not sure if it's a bug or not but, as phpclub said, that action configuration doesn't make a lot sense.

        I would try to streamline it and see if you still get any problem.

        If start from A and (B or C) and (D or E) remove the followin conditions:

        B Application not like OCS-Inventory
        C Application not like ICMP

        As the application will either not be in OCS-Inventory or not be in ICMP, so (B or C) will always equal TRUE

        Also remove:
        E Trigger severity <> Information

        and change:
        D Trigger severity >= High

        to
        D Trigger severity >= Warning

        as any alarm that is not Information has either Warning or higher severity.

        You will end up with the following conditions:
        A Maintenance status not in maintenance
        B Trigger severity >= Warning

        Try them and see if you still have problems.

        Comment

        • phpclub
          Junior Member
          • Jul 2015
          • 7

          #5
          Trigger severity >= High (Only this)

          Trigger severity <> Information
          Trigger severity <> Warning
          Trigger severity <> Average

          this will also be always true.
          if its not information then its warning, since it is OR (I assume) it will pass.

          Use one rule only for example :

          Trigger severity = High

          start simple, when one basic rule works, then start adding others ONE BY ONE, until it stops working, then you know what rule is the problem.

          Comment

          • akbar415
            Senior Member
            • May 2015
            • 119

            #6
            Originally posted by phpclub
            Trigger severity >= High (Only this)

            Trigger severity <> Information
            Trigger severity <> Warning
            Trigger severity <> Average

            this will also be always true.
            if its not information then its warning, since it is OR (I assume) it will pass.

            Use one rule only for example :

            Trigger severity = High

            start simple, when one basic rule works, then start adding others ONE BY ONE, until it stops working, then you know what rule is the problem.
            If my condition is only Trigger severity = High, works fine.
            If is only Trigger severity = Disaster, work fine
            If is only Trigger severity = Warning, work fine

            But if is Trigger severity >= High, or

            A Trigger severity = Warning
            B Trigger severity = High
            C Trigger severity = Disaster

            A or B or C

            I get actions for Information triggers.


            Thanks all for the help. But I I found a solution. I use a script o send the email. So in the script, if the severity was Information, the email was not sended.

            Comment

            • phpclub
              Junior Member
              • Jul 2015
              • 7

              #7
              You have choosen a workaround

              instead of adjusting your actions properly.

              from what you wrote, we conclude that >= is not working well.
              so, we use
              severity <> Information to receive everything else.
              severity = High or severity = Disaster if you want to get just high/disaster.

              really depends on what you're looking for.

              or, you set the severeties you want to receive under the email for that user (which I think is how its supposed to work in the first place).

              anyhow, goodluck with whatever path you decide.

              Comment

              Working...