|
From: Tiago C. <tia...@gm...> - 2016-03-04 17:46:38
|
Hello guys, I'm using zabbix 2.4.7 and Low Level Discovery who parses the output of `varnishadm backend.list` command and send to zabbix, ex: ``` [root@host4 ~]# varnishadm backend.list | column -t | grep apetit -C 2 be_bucket(127.0.0.1,,2676) 1 probe Healthy (no probe) be_apetitar(127.0.0.1,,2677) 3 probe Healthy (no probe) be_adeliveria(127.0.0.1,,2675) 1 probe Healthy (no probe) ``` Everything is working good (the itens are plotting, the graph is working and also the trigger), except for one detail: On the host, I can see lots of "active check "varnish.backends[be_xxxx,conn]" is not supported". And in the server logs, I can see lots of, for example: ``` 7603:20160304:163453.953 item "host4:varnish.backends[be_apetitar,conn]" became supported 7603:20160304:163544.366 item "host4:varnish.backends[be_apetitar,conn]" became not supported: Unsupported item key. 7598:20160304:163654.251 item "host4:varnish.backends[be_apetitar,conn]" became supported 7603:20160304:163738.887 item "host4:varnish.backends[be_apetitar,conn]" became not supported: Unsupported item key. 7600:20160304:163854.747 item "host4:varnish.backends[be_apetitar,conn]" became supported 7610:20160304:163942.025 item "host4:varnish.backends[be_apetitar,conn]" became not supported: Unsupported item key. ``` Even using debug level, I can't understand how to find the root cause of this flapping. Do you have any idea? Thanks! -- -- Tiago Cruz |