Hi All,
I am trying to monitor Tuxedo services on a HP-UX (11.31) Server. I figured the 'proc.num' key would be my best bet, but sadly all I am getting so far are unsupported messages.
I can see the default template is using 'proc.num' for things like sshd, eg; proc.num[sshd]
And they work fine. I am wondering if there is a distinction between zabbix looking for a system service like sshd and looking for another service, like a tux service/handler?
The Tux service, for arguments sake, is called CSS01. If I do a standard "ps -ef | grep CSS01" I see it clear as day, but zabbix doesnt for some reason. Its using the latest agent version (1.8.3) and the same for the server version (1.8.3).
I note some posts in my search talk about the lack of support for proc.num in previous versions, however I wasnt sure if that still persisted into the new versions.
Anyone able to point me in the right direction here?
cheers,
JC
I am trying to monitor Tuxedo services on a HP-UX (11.31) Server. I figured the 'proc.num' key would be my best bet, but sadly all I am getting so far are unsupported messages.
I can see the default template is using 'proc.num' for things like sshd, eg; proc.num[sshd]
And they work fine. I am wondering if there is a distinction between zabbix looking for a system service like sshd and looking for another service, like a tux service/handler?
The Tux service, for arguments sake, is called CSS01. If I do a standard "ps -ef | grep CSS01" I see it clear as day, but zabbix doesnt for some reason. Its using the latest agent version (1.8.3) and the same for the server version (1.8.3).
I note some posts in my search talk about the lack of support for proc.num in previous versions, however I wasnt sure if that still persisted into the new versions.
Anyone able to point me in the right direction here?
cheers,
JC
Comment