Ad Widget

Collapse

host/trigger dependencies with zabbix proxy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • thiago.info
    Junior Member
    • Feb 2008
    • 28

    #1

    host/trigger dependencies with zabbix proxy

    I know that today (2.0.8) Zabbix does not support host dependencies, only trigger dependency. No problem, I just would like some suggestions on how to avoid alerts from the hosts that are monitored through proxy, like "Zabbix agent on HOST is unreachable for 5 minutes".
    Do I need to modify all of my hosts triggers to include a trigger dependency on a trigger that checks my zabbix_proxy availability? If so, is there a way to do it on a bulk way as I have lots of servers?
  • Heilig
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2013
    • 366

    #2
    I can offer at least 4 options:
    1) create dependencies on the template level
    2) create dependencies manually
    3) create dependencies via API
    4) create dependencies using export/import

    The first option I like more than others (example for 3 proxies):
    1) remove all links for the "Template App Zabbix Agent" with other templates (Template OS AIX, Template OS Linux, etc)
    2) "clone" template "Template App Zabbix Agent" in "Template App Zabbix Agent (Proxy 1)", "Template App Zabbix Agent (Proxy 2)", "Template App Zabbix Agent (Proxy 3)"
    3) creates the template "Template App Zabbix Proxy"
    4) in "Template App Zabbix Proxy", create triggers "Zabbix proxy {HOST.NAME} is unreachable"
    5) create the links between triggers "Zabbix agent on {HOST.NAME} is unreachable for 5 minutes" and "Zabbix proxy {HOST.NAME} is unreachable" (in "Template App Zabbix Agent (Proxy 1-3)" and hosts "Proxy1, Proxy2, Proxy3")
    6) link "Template App Zabbix Agent (Proxy 1-3)" to the necessary hosts

    But in general, all depends on the situation (the number of proxies, the current links, number of hosts, etc).
    Last edited by Heilig; 08-09-2013, 22:34. Reason: Updated steps 3)-5)

    Comment

    • Heilig
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Mar 2013
      • 366

      #3
      Also, you can use the "mass update" feature. Create in the "Template App Zabbix Agent" triggers like "Zabbix agent on {HOST.NAME} is unreachable for 5 minutes Proxy #" (eg, "Zabbix agent on {HOST.NAME} is unreachable for 5 minutes Proxy 1", "Zabbix agent on {HOST.NAME} is unreachable for 5 minutes Proxy 2 ", etc). Create a dependency with triggers "Zabbix proxy {HOST.NAME} is unreachable" (on proxy "host level") and then through the "mass update" disable not necessary items on the hosts (for host that is monitored through proxy1 turn off items "Zabbix agent on {HOST.NAME} is unreachable for 5 minutes Proxy 2 ", etc.).

      Comment

      Working...