Ad Widget

Collapse

change default trigger "Zabbix_agentd is not running on {HOSTNAME}"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • just2blue4u
    Senior Member
    • Apr 2006
    • 347

    #1

    change default trigger "Zabbix_agentd is not running on {HOSTNAME}"

    Hi!

    I changed the default trigger "Zabbix_agentd is not running on {HOSTNAME}" from
    Code:
    {tmpl_Linux:proc.num[zabbix_agentd].last(0)}<1
    to:
    Code:
    {tmpl_Linux:proc.num[zabbix_agentd].last(0)}<1|{tmpl_Linux:proc.num[zabbix_agentd].nodata(120)}
    When the Zabbix Agent dies, it can't send data anymore. So the server also needs to check when the last data came from that agent.

    My trigger goes on as soon as there are no more procs called "zabbix_agentd" OR the latest value from proc.num[zabbix_agentd] is 2 minutes old.
    Big ZABBIX is watching you!
    (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)
  • Giors
    Junior Member
    • Aug 2010
    • 5

    #2
    Zabbix agent not working

    I just changed trigger name
    Code:
    Server {HOSTNAME} Zabbix agent not working
    where a value is
    Code:
    {Temp_Linux:status.last(0)}=2
    and set status to high

    Comment

    Working...