Nested macros {$MACRO{MACRO2}}

[karask]

Hello

I'm switching monitoring from Zabbix 1.8 to 2.4.

I have defined Triggers for service state:
Service "ESET HTTP Server" {$SERVICE_STATUS{ITEM.VALUE}} on {HOSTNAME}
and defined global macro:
{$SERVICE_STATUS6} = STOPPED

On Zabbix 1.8 this trigger resolves to
Service "ESET HTTP Server" STOPPED on XXX
but on 2.4 i got:
Service "ESET HTTP Server" {$SERVICE_STATUS6} on XXX

Should I do something more on 2.4 or is it a bug (or kind of feature)?

[quejinho]

In that expresion is there a # instead of = ? Might be just my eyes.

[karask]

In that expresion is there a # instead of = ? Might be just my eyes.

Yes there is # (screen from v1.8). In 2.4 it is <> meaning "not equal".
service_state[] returns 0 if the service is running, so my trigger is executed while there is something wrong. This part is working well, trigger is fired, but its name is wrong.