Multiple UserParameter and wildcards issue

[Shoikan]

Folks,

I've been writing some scripts to monitor Oracle databases (yes, I've seen zabora, but as a good nerd is supposed to do, I've tried to re-invent the wheel). These scripts need to run at the client, so are added to the zabbix_agentd.conf. Now I've run into a few (minor, but very annoying) problems:

• If I user 1 UserParameter item with a wildcard, it works. If I use 2 or more, then the 2nd (and subsequent) ones are shown as 'unsupported'.
• If I try to use a name for the item with a dot (for instance oracle.listener[ *]), it will show up as 'unsupported'. If I remove the dot, it works.

Is this expected behaviour, or is this a bug?

[rbenea]

Can you post the exact config that you have in zabbix_agentd and how the item key looks?

I played today with something like this and it works:

key on the web:
s.script[arg1,arg2]

zabbix_agentd.conf:
UserParameter=s.script[*],/usr/bin/php /usr/bin/script.php $1 $2

Hope that helps,
Rares

[Shoikan]

Hmmm.. I just noticed I was having some weird issue.. Wellllll.. weird.. Zabbix (serverside) runs on a linux box. The client(s) is a Tru64 cluster. When you connect to the cluster alias, you can more or less randomly end up on one of the 4 nodes making up the cluster. I was fiddling on one of the cluster nodes, and zabbix would sometimes end up on the right one, but most of the times on the wrong one.... I will have to doublecheck what happens now I have realised this and make them all 'equal'.