Ad Widget

Collapse

Agent availability, trigger dependencies

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tommycz
    Junior Member
    • Apr 2011
    • 10

    #1

    Agent availability, trigger dependencies

    Hello,
    I have some hosts behind zabbix proxy. In template for zabbix_proxy I defined item zabbix[proxy,<proxy_name>,lastaccess] with trigger zabbix[proxy,<proxy_name>,lastaccess].fuzzytime(180)}=0 for checking hearbeat of proxy.
    <proxy_name> is the name of proxy.

    In another template for linux servers I defined item for check of agent availability -- agent.ping with trigger agent.ping.nodata(180)}=1

    Now I need to ensure: if proxy won't be available,then don't activate trigger in linux template agent.ping.nodata(180)}=1

    Unfortunately trigger dependencies between templates are not allowed.Is there any workaround?

    Thank you
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    in 1.8, the best bet probably is to mass-update trigger dependencies. if more complex rules are required, scripted api updates might help.

    in 2.0, depending from template to host triggers will be supported, which might help with this as well
    Zabbix 3.0 Network Monitoring book

    Comment

    Working...