"No such monitored parameter" when adding new trigger

[goony]

Zabbix V1.4.5, compiled & installed on Solaris V9, new Zabbix user.

I've looked through the docs and maybe I'm missing some kind of fundamental concept: I want to create a trigger to fire if a particular named process is missing. This process isn't one of the default missing process triggers (inetd, sshd, syslogd, etc.) that are part of the out-of-the-box Zabbix install.

On the Zabbix server, I'm in Configuration-->Triggers and choose an existing trigger that looks like this:

Name: Inetd is not running on {HOSTNAME}
Expression: {myclientroc.num[inetd].last(0)}<1

So... I figured I could just clone the above trigger and modify the inetd part to become the process name that I wanted, but no dice - I get this error when trying to save the new trigger:

No such monitored parameter (proc.num[nsrd]) for host (myclient)

Do I need to modify my /etc/zabbix/zabbix_agentd.conf file to define something so that I can have a trigger fire when process nsrd is missing?

Thanks!

[nelsonab]

Name: Inetd is not running on {HOSTNAME}
Expression: {myclientroc.num[inetd].last(0)}<1

So... I figured I could just clone the above trigger and modify the inetd part to become the process name that I wanted, but no dice - I get this error when trying to save the new trigger:

No such monitored parameter (proc.num[nsrd]) for host (myclient)

Do I need to modify my /etc/zabbix/zabbix_agentd.conf file to define something so that I can have a trigger fire when process nsrd is missing?

It's likely you forgot to add proc.num[nsrd] as a key for the host "myclient". I know it seems counter-intuitive but that's how it works. Pretty much everything is centered around the key field.

[goony]

Closer, but still no joy.

On the client system, added to /etc/zabbix/zabbix_agentd.conf:

UserParameter=proc.num[nsrd],/usr/bin/pgrep -x nsrd|wc -l

Restart the agent; get an error:

bash-2.05$ /usr/local/sbin/zabbix_agentd &
[1] 28874
bash-2.05$ zabbix_agentd [28874]: Warning: Can't add user specifed key "proc.num[nsrd]". Incorrect key!

Any further suggestions?

Thanks!

[boy01]

Closer, but still no joy.

On the client system, added to /etc/zabbix/zabbix_agentd.conf:

UserParameter=proc.num[nsrd],/usr/bin/pgrep -x nsrd|wc -l

Restart the agent; get an error:

bash-2.05$ /usr/local/sbin/zabbix_agentd &
[1] 28874
bash-2.05$ zabbix_agentd [28874]: Warning: Can't add user specifed key "proc.num[nsrd]". Incorrect key!

Any further suggestions?

Thanks!

I've found out that I can't use [] chars in my UserParameter specs.
So I'd change your example to:
UserParameter=my_proc_num_nsrd,/usr/bin/pgrep -x nsrd|wc -l

[nelsonab]

You're getting close. You'll need to go back to some of the basics. As much as I rail against it the manual is a good reference here.

In your zabbix_agent(d).conf file try this
UserParameter=my_proc_num,/usr/bin/pgrep -x $1|wc -l

Then go to config-> host and setup a host entry for this machine.
Then go to config->items and setup an item entry.

Desc: Number of NSRD processes running
key: my_proc_num[nsrd]
type: number
interval: however often you want
store as: as is


Now go to Monitoring->latest data, select the host, you should now see the item you just added in this list. Now this key is ready to be used in a trigger.