Issue with triggers on disabled web scenario

[StCyr]

Hello,

I've a configuration that results in something weird:

I've a template that defines 3 web scenario (let's call them WB1, WB2, and WB3) and 3 corresponding triggers (let's call them T1,T2, and T3).

WB2 and WB3 are disabled by default; Admins should enable them on a host-by-host basis when they want more than just WB1.

My expectation is that T2 and T3 shouldn't report a problem when WB2 and WB3 are disabled.

But, for some reason, T2 reports a problem:



I would expect that either niether or both T2 and T3 report a problem. But, here, I'm a little bit baffled when only T2 report a problem.

Any idea why I'm getting this result? Or how to properly configure my triggers to not report a problem when the web scenario is disabled (Yes, I know I can also disable the trigger by default)?

[azyla]

Hi,

It is hard to pinpoint the best possible solution here, however it seems like the issue lays within Problem expression of the T2 and you should manipulate with it a bit so it does not report a problem when WB2 and WB3 are disabled.
Also could be worth playing around with Recovery expression of T2 as well so the reported problem is automatically resolved when T3 does not fire a problem at the same time.

This particular page from official Zabbix documentation may come in handy: 2 Trigger expression (zabbix.com).

Hope it helps.

Regards,
Arkadiusz

[cyber]

Sisabling web scenario does not disable trigger automatically... it makes items not supported. What kind of trigger expressions you have there? There can be cases, where trigger is still calculated, when item values are not known https://www.zabbix.com/documentation...known-operands

[StCyr]

The original trigger expressions were:

last(/SRV - Simple web monitoring/web.test.fail[Simple web check 1])<>0

and

last(/SRV - Simple web monitoring/web.test.fail[Simple web check 2])<>0

Since I thought that it could trigger because of the unsupported items, I've decided to change them to

last(/SRV - Simple web monitoring/web.test.fail[Simple web check 1])<>0 and nodata(/SRV - Simple web monitoring/web.test.fail[Simple web check 1],600)<>1

but it doesn't change anything.

Maybe my only option is to disable those triggers when their respective web scenario are disabled....