Ad Widget

Collapse

Trigger condition: "trigger name" not working as I expect

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ivanni
    Junior Member
    • Mar 2015
    • 15

    #1

    Trigger condition: "trigger name" not working as I expect

    Hello,

    I am using Zabbix server 2.4.4.

    I have 1 host group with several hosts. Our company has 1st line support and 2nd line support.
    So for these hosts I have configured some triggers who are for the 1st line support, e.g. their name starts with: SUPP1 CPU load is {ITEM.LASTVALUE1}
    And I have configured some triggers who are for the 2nd line support, e.g. their name starts with: SUPP2 PostgreSQL active connections: {ITEM.LASTVALUE1}

    Everything is OK, but I want to receive emails only for SUPP2 triggers, so I configured this action:

    Trigger value = PROBLEM
    Trigger name not like SUPP1
    Host group = MYHOSTGROUP

    Send message to user groups: GROUP-SUPPORT-2 via Email

    The problem is that I continue to receive all triggers including the SUPP1 triggers. Why? And how to configure the action like that to receive only SUPP2 triggers?

    Thank you!
  • Linwood
    Senior Member
    • Dec 2013
    • 398

    #2
    Is that the only trigger, could you be getting them from a different trigger?

    I assume there's an AND in all of those?

    Comment

    • ivanni
      Junior Member
      • Mar 2015
      • 15

      #3
      @Linwood, thank you for your reply.

      No, I am not getting these mails from different trigger action. I have only this action.

      And yes: there is an AND between the conditions... Does this work for you? Or is there any other solutions to achieve what I am looking for?

      Comment

      • Linwood
        Senior Member
        • Dec 2013
        • 398

        #4
        I don't use it normally but in a quick test it seemed to work. I just cloned a trigger and added a condition to the clone with different destination. I got messages at the destination only when the trigger name didn't contain the string.

        I'm on 2.4.6rc1.

        Comment

        Working...