Processes of interpreters

[flycat]

How it is possible monitorit quantity of the processes started on various interpreters, for example

usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -p 8500 -a 212.69.109.119 -l /www/projects/announce_1/log -P /www/projects/announce_1/log/mongrel_cluster.8500.pid --user announce-www --group www

Or quantity of identical processes with different parameters?
Now a can monitor only `ruby' processes, not `mongrel_rails' (or other)
Is it internal grep analog in zabbix?

[Alexei]

proc.num[ruby,,,mongrel_cluster]

The third parameter filters processes by command line parameter. See ZABBIX Manual for more details.

[flycat]

Thanx a lot!

[flycat]

WTH!
We explore Zabbix don't check ruby processes. Perhaps, Zabbix use proc filesystem? But on kernels 2.6.x in SLED9,10 found:

cat /proc/9456/cmdline
/usr/local/bin/ruby/usr/local/bin/mongrel_railsstart-d-eproduction-p8500-a212.69.109.119-l/www/projects/announce_1/log-P/www/projects/announce_1/log/mongrel_cluster.8500.pid--userannounce-www--groupwww

i.e. cmdline file do not contain spaces between parameters and Zabbix don't cut command line parameters. This bug (?) found on java, python and ruby applications.

[Alexei]

This is fixed in pre 1.4.1.

[flycat]

proc.num[ruby,,,mongrel_cluster]

The third parameter filters processes by command line parameter. See ZABBIX Manual for more details.

1. I study ZABBIX Manual (v.1.4 rev 9):

proc.num[<name><,user><,state>]

2. Shell script running by bash don't monitoring with proc.num[bash,,,script] Zabbix 1.4.2

[Alexei]

The manual does contain decription of proc.num[<name><,user><,state><,cmdline>].

[flycat]

The manual does contain decription of proc.num[<name><,user><,state><,cmdline>].

Yes, I got it! Thank you! And what about bash script?