Hi,
First, a compliment. Thank you for all of your work on Zabbix. The more I use it, the more I like it!
proc.num question (feature request?)
We use Novell Identity Manager. One of our Linux Systems, runs a daemon called usdrv. If you do "ps -ef | grep usdrv", one process should be displayed.
But when I would query the number of usdrv procs with Zabbix, using "zabbix_get -slocalhost -kproc.num[usdrv]" it would always return 7.
I then found that if I added the "-m" switch to my ps command, which means "show all threads" to ps, it would show 7 usdrv procs. OK, now I understood where Zabbix was getting 7.
It would be nice to be able to control how Zabbix counts processes with "proc.num" in the same way one can with the ps command. If this is already possible and I just missed it, please let me know.
I bring this up because if we have a problem with one of the usdrv scripts, "ps -ef | grep usdrv" will show more than 1 proc, while when it is correctly running, it will only show one. To be able to trigger for "not 1" would be nice.
net.tcp.service
How do I get a service recognized by zabbix? Here's what I'm having trouble with. Our IDM system, as mentioned above, listens on port 8090. I tried querying it with "zabbix_get -slocalhost -knet.tcp.service[idm,127.0.0.1,8090]", after making sure the service was up and listening on that port/IP. I'd get back "ZBX_NOTSUPPORTED."
I assumed this meant Zabbix didn't know what the "idm" service was. So I edited /etc/services and added a line for it and restarted the server. zabbix_get still wouldn't work.
As a guess, I then did "zabbix_get -slocalhost -knet.tcp.service[ftp,127.0.0.1,8090]", which worked. The service listening on port 8090 is not FTP, but by calling it ftp instead of an unrecognized name, zabbix was able to query it.
So, how do I add service names to zabbix? It seems to me it should just use ones from /etc/services. Also, it doesn't make sense to me that zabbix would fail using 'idm' but work with 'ftp' when the service is not an ftp service. It mustn't be doing a protocol check or it would fail when I used 'ftp', so why should it care what name I use anyway?
In the meantime, I am just using net.tcp.port[localhost,8090], which works fine.
Thanks,
Ted
First, a compliment. Thank you for all of your work on Zabbix. The more I use it, the more I like it!
proc.num question (feature request?)
We use Novell Identity Manager. One of our Linux Systems, runs a daemon called usdrv. If you do "ps -ef | grep usdrv", one process should be displayed.
But when I would query the number of usdrv procs with Zabbix, using "zabbix_get -slocalhost -kproc.num[usdrv]" it would always return 7.
I then found that if I added the "-m" switch to my ps command, which means "show all threads" to ps, it would show 7 usdrv procs. OK, now I understood where Zabbix was getting 7.
It would be nice to be able to control how Zabbix counts processes with "proc.num" in the same way one can with the ps command. If this is already possible and I just missed it, please let me know.
I bring this up because if we have a problem with one of the usdrv scripts, "ps -ef | grep usdrv" will show more than 1 proc, while when it is correctly running, it will only show one. To be able to trigger for "not 1" would be nice.
net.tcp.service
How do I get a service recognized by zabbix? Here's what I'm having trouble with. Our IDM system, as mentioned above, listens on port 8090. I tried querying it with "zabbix_get -slocalhost -knet.tcp.service[idm,127.0.0.1,8090]", after making sure the service was up and listening on that port/IP. I'd get back "ZBX_NOTSUPPORTED."
I assumed this meant Zabbix didn't know what the "idm" service was. So I edited /etc/services and added a line for it and restarted the server. zabbix_get still wouldn't work.
As a guess, I then did "zabbix_get -slocalhost -knet.tcp.service[ftp,127.0.0.1,8090]", which worked. The service listening on port 8090 is not FTP, but by calling it ftp instead of an unrecognized name, zabbix was able to query it.
So, how do I add service names to zabbix? It seems to me it should just use ones from /etc/services. Also, it doesn't make sense to me that zabbix would fail using 'idm' but work with 'ftp' when the service is not an ftp service. It mustn't be doing a protocol check or it would fail when I used 'ftp', so why should it care what name I use anyway?
In the meantime, I am just using net.tcp.port[localhost,8090], which works fine.
Thanks,
Ted
Comment