Ad Widget

Collapse

Problem identifying trigger dependency

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bytesize
    Member
    • Aug 2005
    • 71

    #1

    Problem identifying trigger dependency

    Hi guys,

    I have a number of routers, all of which have the same trigger name "Router Ping Response" - this is so all the routers appear on the same trigger line in the status overview. The same applies to the firewalls which sit behind the routers, they all have the trigger "Firewall Ping Response".

    However I have a problem when it comes to telling the trigger to depend on the router in the trigger - all the triggers for all the firewalls are called "Firewall Ping Response!"

    Is there any way of better identifying which dependency relates to which hostname, or am I just doing this completely wrong?

    Thanks!

    John
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    I believe you're doing everything right. The drop-down has to be fixed to include also hostnames.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • globifrosch
      Member
      • Sep 2005
      • 74

      #3
      hi

      is this problem about identifying dependencies going to get fixed in 1.1? as in 1.1beta2 this problem still exists.

      thx!

      Thomas

      Comment

      • bytesize
        Member
        • Aug 2005
        • 71

        #4
        Hi,

        Yes this problem still seems to exist, which means I cant identify a specific hosts dependency from a huge list which all say the same thing!

        Just eing able to add a variable like $HOSTNAME to the trigger name would solve the problem.

        John

        Comment

        • amemrdijk
          Junior Member
          • Jun 2006
          • 1

          #5
          Same problem here. Suggestions?

          Comment

          • adam.vollrath
            Member
            • Apr 2006
            • 31

            #6
            You can add {HOSTNAME} to the trigger name.

            Comment

            Working...