Ad Widget

Collapse

Action conditions > Type Of Calculation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Capdefava
    Junior Member
    • Aug 2011
    • 6

    #1

    Action conditions > Type Of Calculation

    Hi All:

    Does anyone know how I can configure this type of conditions calculation?

    (A) Trigger value = PROBLEM
    (B) Trigger = "MyTriggerPingFailure"
    (C) Trigger value = PROBLEM

    A AND NOT (B AND C)

    I mean, run the action when any trigger value was PROBLEM except if trigger "MyTriggerPingFailure" value is PROBLEM.

    I don't want any action for any trigger PROBLEM if the problem is due a connection failure (MyTriggerPingFailure PROBLEM)

    Thank you.

    Regards,
    CPF
  • hirschnf
    Member
    • Jan 2010
    • 56

    #2
    As I understand you, this action should fire every time a trigger is in problem state but if the trigger "MyTriggerPingFailure" is in problem state it should not fire?

    Perhaps you can do

    AND
    (A) Trigger value = PROBLEM
    (B) Trigger <> "MyTriggerPingFailure"

    I did not test this...

    Comment

    • Capdefava
      Junior Member
      • Aug 2011
      • 6

      #3
      Yes, you've understood correctly.

      AND
      (A) Trigger value = PROBLEM
      (B) Trigger <> "MyTriggerPingFailure"


      I just test and this does not work, because this condition run the action always that trigger = PROBLEM if the trigger is not "MyTriggerPingFailure"

      Thanks anyway!

      Comment

      • hirschnf
        Member
        • Jan 2010
        • 56

        #4
        Ok, I've tested now.
        First trigger was the Processor Time Percent . If the processor is more than 90% busy the trigger goes to "Problem" state.
        The second trigger was the percentage use of drive c:
        If free space is lower than 2% the trigger goes to "Problem" state.

        Trigger value = "PROBLEM"
        Trigger <> "pcxx:Low free disk space on {HOSTNAME} volume c: in Percent"

        The result was one "Problem" mail because the CPU Trigger and a second mail for the "OK" State of the CPU trigger.
        The free space trigger was ignored.

        As I understand your problem with these conditions the action runs as I expected.

        Comment

        • Capdefava
          Junior Member
          • Aug 2011
          • 6

          #5
          Thank you

          Finally I did it with 'trigger dependencies' not very confortable if you need to use with a lot hosts/triggers but it works....

          http://www.zabbix.com/documentation/...r_dependencies (the example is very similar to my case)

          Comment

          Working...