Zabbix 1.8.10 and trigger behaviour

[mbconn]

I have a number of triggers I use to check that certain external services are available via both our primary and secondary Internet links. These are of the form:

{host:icmpping[].last(0)}=0 & {hosting_backup.sh.last(0)}=0

So, if the host is unavailable via both the primary and secondary links I'd expect to see 3 events:

host unreachable via Primary
host unreachable via Secondary
host unreachable via Primary and Secondary (in turn triggers an action)

Up until now this has worked pretty successfully, but since our upgrade to 1.8.10 whenever the second part of the expression is true, i.e. the

{hosting_backup.sh.last(0)}=0

I also get an event saying the whole expression has triggered, i.e.

host unreachable via Secondary
host unreachable via Primary and Secondary

The associated action doesn't trigger, but the problem is consistent. Is this a bug in 1.8.10 or a change in behaviour?

thanks
Mike

[mbconn]

Just to clarify, the "combined" trigger is:
Server unreachable via {$PRIMARY} and {$SECONDARY}

{Template_My_Generic:icmpping[].count(#3,0)}>2 & {Template_My_Genericing_backup.sh.count(#3,0)}>2

This trigger shows as an event every time the second part of the statement is true, event though the first part isn't true.

[mbconn]

Resolution

I appear to have solved this by reordering the triggers. Zabbix seems to order them alphabetically, so they were appearing as:

host unreachable via Primary
host unreachable via Primary and Secondary (in turn triggers an action)
host unreachable via Secondary

By simply changing the description so that they are ordered:

host unreachable via Primary
host unreachable via Secondary
host unreachable via Secondary and Primary (in turn triggers an action)

the "Secondary and Primary" trigger only gets fired if both the Primary and Secondary routes are down.