Trigger doesn't fire

[ringmaster]

Hi there,

I've got a problem with my Zabbix installation:
I want to monitor a few webservices on a single machine so I installed a zabbix agent and server on the same machine.
I made all the configurations I needed, including generating web scenarios and triggers.

My problem is now:
if I deactivate one of the webservice I can see the error at Monitoring->Web. So far so good. Unfortunately the trigger doesn't seems to fire so there isn't any problem showing up on the dashboard.
As I'm already using Zabbix on another enviroments with multiple servers which is working pretty well I currently have no idea why the trigger doesn't lead to a Probleme message.
Does anyone have any idea what I could check to solve this issue?

[gert.derouck]

Please paste screenshots of the involved items and triggers; and of the latest data that should trigger the problem.

[mfortes]

Are u check your webservices responde code?
If u not, do't...
Soo you can create a trigger where "fire" when the last data isn't 200.

[ringmaster]

My webscenario checks the response code of a given URL. In this case the response code needs to be 302.
It seems that the check itself is working, as it shows an error in the latest data if I shut down the webservice. Also in the Monitoring->Web area you can see an info about the failed test.
The only thing which isn't working is triggering a Warning then.
I made two screenshots (had to blur some sensitive parts). Does this help?
Im using a similiar configuration in a different enviroment with multiple servers and it's working pretty well so I'm really wondering what I 've missed here.

[ringmaster]

I think I found the problem which causes the behaviour.
My expression for the trigger was set to
web.test.fail[...].last() > 2
As I only wanted to get a notification after the check failed more then twice. This doesn't seem to work, so I changed it to >0 and now the trigger generates a Problem.
I think my assumption was wrong.

Is this normal or were ther any changes in the latest version?
Cause as I said I'm using the same Expression (>2) in another enviroment without any issues but it's running on version 4.2 instead of 4.4 in the new enviroment. Im wondering why it works on this enviroment.

[gert.derouck]

Hi Ringmaster,
from https://www.zabbix.com/documentation...nitoring/items

This item will display the number of the step that failed on the scenario. If all steps are executed successfully, 0 is returned. Item key: web.test.fail[Scenario] Type: Numeric(unsigned)

So it depends on the number of steps you have...

If you want it to fail only after 2 probes you can use: web.test.fail[...].min(#2)>0

[ringmaster]

If you want it to fail only after 2 probes you can use: web.test.fail[...].min(#2)>0

Great, Thank you for this hint. I'm going to give it a try in my enviroment.