-
Incident report
-
Resolution: Won't fix
-
Trivial
-
None
-
None
-
None
According to documentation, host ip and dns is used in net.tcp.service.
However, we have a host that have a port bonding on ip address. However, Zabbix couldn't see the port up unless specifying hostname or macro {HOST.NAME} in the key.
https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/simple_checks
net.tcp.service.perf[service,<ip>,<port>]
ip - IP address or DNS name (by default, host IP/DNS is used)
# client side 984|[[email protected] ~]$ netstat -ant|grep LISTEN|grep :8 tcp 0 0 10.24.70.181:8300 0.0.0.0:* LISTEN tcp 0 0 10.24.70.181:8301 0.0.0.0:* LISTEN tcp 0 0 10.24.70.181:8302 0.0.0.0:* LISTEN tcp6 0 0 :::8080 :::* LISTEN tcp6 0 0 :::8400 :::* LISTEN tcp6 0 0 :::8500 :::* LISTEN tcp6 0 0 :::8600 :::* LISTEN
982|[[email protected] ~]$ zabbix_agent -V Zabbix agent v2.2.11 (revision 56693) (12 November 2015) Compilation time: Nov 13 2015 08:29:41
zabbix side
982|[[email protected] ~]$ zabbix_get -s 3.example.com -k net.tcp.service[http,,8300] 0 984|[[email protected] ~]$ zabbix_get -s 3.example.com -k net.tcp.service[tcp,3.example.com,8300] 1 # By default it should use the ip or DNS. 984|[[email protected] ~]$ zabbix_get -s 3.example.com -k net.tcp.service[tcp,,8300] 0