Monitoring a TCP port on host from zabbix server

[rks]

Env:
Zabbix server 2.4.6 on Centos 6.5
Host: CentOS 6.5

The monitored host has a tcp service tcp/3306. I want to define an alarm when the service is not reachable.

I defined a simple check on net.tcp.service[service,,3306]
And I defined a trigger
{host.xxx.com:net.tcp.service[tcp,,3306].last()}=0

After I define the trigger, the trigger goes into "Unknown" state with the "Info" column stating:
"Invalid first parameter"



However, this works for the item:
net.tcp.service[http,,8080]

Could you pl let me know why I cannot similarly monitor tcp/3306 as I am monitoring tcp/8080

Thanks,

/Kobe

[gleepwurp]

Hi Rks,

Well, the item defined on your host and its trigger should have the same definition...

I see in your example that your item is defined as:

net.tcp.service[service,,3306]

However your trigger is defined as:

{host.xxx.com:net.tcp.service[tcp,,3306].last()}=0

(see the differences in bold).

Unless I'm mistaken, your item should be:

net.tcp.service[tcp,,3306]


G.