Ad Widget

Collapse

Selective alerting?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • hughmcl
    Junior Member
    • Oct 2008
    • 20

    #1

    Selective alerting?

    Is there a way to send only selected alerts to email/sms?

    e.g. we monitor 20 machines, but our helpdesk person only wants to receive 20 alerts out of the 400 we generate. Is there an easy way to set it up so that the user can pick what triggers they get alerts about? I know theres a way to kind of do it with the actions/action conditions, however for these alerts, I'd have to create lots of rules, or is there an easy way?

    (Using Zabbix 1.6.4)

    Hugh
    Last edited by hughmcl; 21-05-2009, 01:42.
  • bobrivers
    Senior Member
    • Feb 2007
    • 115

    #2
    Actions conditions

    Well, we do this using actions conditions.

    For instance, if they want to receive just when the host is unreacheable for a specific host, create an action with a trigger and host conditions.

    In fact this zabbix feature is quite flexible.

    Regards,

    Bob

    Comment

    • hughmcl
      Junior Member
      • Oct 2008
      • 20

      #3
      Well i know about that. The issue is that we have 20 servers, and they wnat to know about 15 services on each server, and they are different services on each server. From what I can tell from the actions/action conditions I'd have to set up over 100 rules to be able to do the above combinations. Thought there might be an easier way where you could assign a trigger to belong to notification groups. That way you add the trigger to the group, rather than having to filter it at the alerting point.

      Comment

      • bobrivers
        Senior Member
        • Feb 2007
        • 115

        #4
        trigger description

        Use trigger description. Modify it and add, for instance, "hdesk". Then, when building the actions use

        trigger description like hdesk

        Comment

        • bashman
          Senior Member
          • Dec 2009
          • 432

          #5
          It seems that trigger description refers to the trigger comments field, not to the trigger name field.

          I have actions for groups of hosts, but I don't want to alert tomcat admin or mysql admin about the Zabbix Agent, only to zabbix admin.

          So in tomcat actions or mysql actions I have a condition:
          Trigger description not like "Inactive Zabbix Agent"

          Which is the name of this trigger:
          {hostname:agent.ping.nodata(600)}=1

          And I had no commets, but tomcat admin and mysql admin had alerts about Zabbix Agent, so the condition didn't work.

          Adding this line: "Inactive Zabbix Agent" to the comments field it worked fine.
          978 Hosts / 16.901 Items / 8.703 Triggers / 44 usr / 90,59 nvps / v1.8.15

          Comment

          • MrKen
            Senior Member
            • Oct 2008
            • 652

            #6
            @bashman,

            Sorry, I can't agree with that. I have a number of Actions with conditions of 'Trigger description not like <blah>' and they work fine.

            None of my Triggers have any comments.

            From the online documentation:
            Trigger description (name) = Compare against Trigger Name which generated event.
            http://www.zabbix.com/documentation/1.8/manual/config/actions

            regards,
            MrKen
            Disclaimer: All of the above is pure speculation.

            Comment

            • bashman
              Senior Member
              • Dec 2009
              • 432

              #7
              Thanks MrKen.

              Well, I don't know then, why my trigger condition "Trigger Description not like" didn't work for me.

              I have seen the Zabbix wiki, you're right, that's what it says, and that's what I've tried, but it didn't work.

              So I tried writing in the trigger comments field the name of the trigger and it worked fine.

              I don't know the reason for this.
              978 Hosts / 16.901 Items / 8.703 Triggers / 44 usr / 90,59 nvps / v1.8.15

              Comment

              Working...