Question about "Global" Regex's

[danrog]

I haven't found too much info on the regex's you can enter under Admin -> General -> Regexp's so I thought I'd ask here. The documentation states ".. it can be used everywhere regular expressions are supported by referring to it's name, prefixed with @, for example, @mycustomregexp." however, it doesn't seem to work with the item web.page.regexp. Are these global regex's only meant to be used with triggers?

Here is an example:

web.page.regexp[server,/path/monitor.display,8080,@SmokeTest]

[richlv]

could you please report this on the tracker ?
thanks

[danrog]

Will do, I just didn't want to do that first in case it was expected behavior and not supported.

[lukemacneil]

Same for log items. I'm having the same problem with 1.8.5
Did you ever find a workaround for this?

[simon123]

@prefix doesn't work with macro's either

I would like to see this feature better documented as well, the @prefix doesn't seem to be accepted when combined with macro's either

Incorrect trigger expression format " {constant}>{constant} & {constant} = @PublicIP "
Check expression part starting from " {C_Template_SNMPv2_Interfaces14:ifInOctets.14.last(0)}>{$MAXIN} & {$IF14} = @PublicIP "

({$IF14} being the ip address of the interface)

EDIT:

I worked around this issue by querying for the IP-adr instead of using the one i have stored in a macro.

{C_Template_SNMPv2_Interfaces11:IPAdrEntIP.11.regexp(@PublicIP)}

This works like a charm though

Maybe the regexp on macro's could be supported in triggers in a future release...

[richlv]

trigger functions may only return numbers, as per manual, thus comparing two textual values is not possible at this time (as far as i know )