Macro as community name in SNMP check

[Calypso]

Documentation of version 1.8.4 says that you can now use a Macro as the community name. When I try this, it seems that it doesn't work. I've tried several scenarios: macro at hostlevel and in template, and item direct on a host and in a template.

Does anyone have a better experience with this feature, and how did you implement it?

[richlv]

hmm. i can't find that at the moment, where does it state that it's supported in 1.8.4 ?

[Calypso]

This https://support.zabbix.com/browse/ZBXNEXT-355 states that it is available in 1.8.4rc3

[richlv]

hmm. then it probably should work
did you doublecheck that it's 1.8.4 ? how exactly did you try to use them ?

[SpiderX]

Does anyone have a better experience with this feature, and how did you implement it?

I'm using it. Its working fine for me.
I defined a Macro in template.

[Calypso]

I'm sure I'm using 1.8.4 (final). What I did was put a macro in the template (and later also in the host): {$COMSTRING} = "public", and {$COMSTRING} in the community field. Strange - I'll dive further into it tomorrow...

[Calypso]

Found the problem. In other uses of the Macro functionality I had to put quotation marks around the macro value to let it work. With the community, the quotation marks leads to the malfunction.

So without the quotation marks it works...

[richlv]

hmm. could you please clarify where you had to use quotes and what were th macro contents in those cases ?

[Calypso]

When I pass a macro as an argument for a check by script, (say I want to use "Notepad" as a parameter for the script) it is only recognized by the script when I use the quotes around it.

Now, I must say that I use that feature since quite some time, so maybe the behaviour has changed.

[richlv]

hmm. that should only be required if the parameter includes spaces or other potentially problematic characters - simple alphanum char string should work fine without quoting as well