Hi everyone! I'm a new user to Zabbix and I'm currently transitioning my Nagios checks to Zabbix. So far it's going great 
I stumbled upon one problem and that is with net.tcp.service.perf[service,<ip>,<port>]
I set Zabbix Agent item to check performance of SSH like this:
net.tcp.service.perf[ssh,,1022]
The problem is that this item should return 0 if the service is down and number of seconds if it's up. But what happens if it takes 0 seconds to reach the SSH server, since it is accessed localy? How would Zabbix know if the service is up or down then? I made a trigger which looks like this:
{Template OS Linux:net.tcp.service.perf[ssh,,1022].last(0)}=0
And this trigger is always telling me that SSH is down and I know it is up. Wouldn't it be better if this item returned -1 if there is a problem with the service, or is there a better way to write this trigger?
I also noticed that this item only works on the Zabbix Server which is running a Zabbix agent, it doesn't want to work on other servers with a Zabbix agent.
Thanks in advance.

I stumbled upon one problem and that is with net.tcp.service.perf[service,<ip>,<port>]
I set Zabbix Agent item to check performance of SSH like this:
net.tcp.service.perf[ssh,,1022]
The problem is that this item should return 0 if the service is down and number of seconds if it's up. But what happens if it takes 0 seconds to reach the SSH server, since it is accessed localy? How would Zabbix know if the service is up or down then? I made a trigger which looks like this:
{Template OS Linux:net.tcp.service.perf[ssh,,1022].last(0)}=0
And this trigger is always telling me that SSH is down and I know it is up. Wouldn't it be better if this item returned -1 if there is a problem with the service, or is there a better way to write this trigger?
I also noticed that this item only works on the Zabbix Server which is running a Zabbix agent, it doesn't want to work on other servers with a Zabbix agent.
Thanks in advance.
Comment