HTTP status alerts

[pridetechdesign]

Hi, I've got an HTTPS status check cloned from an HTTP status check. I changed the http service is running to https service is running and changed net.tcp.service[http] to net.tcp.service[http,,443], however when I set up a test environment to throw a 403, zabbix does not alert. It is supposed to alert if it receives anything that isn't a 200, so what am I doing wrong?

[unficyp]

I guess the check should be net.tcp.service[https] not http
If you just want to know if the port is open use net.tcp.service[tcp,,443]

[pridetechdesign]

Here is the error the server presents:

cannot process step "domain.net http check" of web scenario "domain.net" on host "domain.net": response code "403" did not match any of the required status codes "200"

That's great so far right? but why isn't it setting off the trigger? It is supposed to.

[unficyp]

Is it possible that you mix up 2 things ?

In your first post you write:
net.tcp.service, which is a simple and/or agent check

In your second post you write "of web scenario".

Do you have both ?
The simple/agent check should read "net.tcp.service[https]", you missed the s in https there.
Otherwise post your trigger and/or your complete web scenario please.

[pridetechdesign]

Is it possible that you mix up 2 things ?

No.

Please see the error message I excerpted from the server log, as I believe it is relevant but I do not know how to solve it.

These alerts used to work. I am planning to upgrade to 3.0 as it appears to be out of beta, and with that I'll be changing from simple checks to agent checks, but I would like to understand and resolve this issue first.

[unficyp]

Just tried this at our test server, i have the same lines in the log but the trigger is firing.

Trigger definition:
{test1:web.test.fail[test_web_scenario].last()}>0

Maybe you can set a higher debug level for zabbix server logging to see why the trigger doesn't fire.
Another possibility may be that actions are disabled either in the global or user configuration.

[pridetechdesign]

bumping because this is still an issue and none of the advice so far has produced a solution.

I've got logging at debug level and here is the information from the web availability test:

15270:20160428:142917.590 In evaluate_function() function:'HOSTNAME.net:net.tcp.service[https].max(#3)'
15270:20160428:142917.590 In evaluate_MAX()
15270:20160428:142917.590 In __get_function_parameter_uint31() parameters:'#3' Nparam:1
15270:20160428:142917.590 In substitute_simple_macros() data:'#3'
15270:20160428:142917.590 __get_function_parameter_uint31() flag:1 value:3
15270:20160428:142917.591 End of __get_function_parameter_uint31():SUCCEED
15270:20160428:142917.591 In zbx_vc_get_value_range() itemid:24976 value_type:3 seconds:0 count:3 timestamp:1461868156
15270:20160428:142917.591 End of zbx_vc_get_value_range():SUCCEED count:3 cached:1
15270:20160428:142917.591 End of evaluate_MAX():SUCCEED
15270:20160428:142917.591 End of evaluate_function():SUCCEED value:'1'

It should be triggering, because the website is currently throwing a 403 error, but it's not triggering. If I shut the webserver down it triggers, but it doesnt trigger for a 403 error, or 404, or 500, etc. This seems like a bug to me.

Any help is appreciated.

[pridetechdesign]

bump

I just wanted to bump this (I hope that's okay?) because it seems like a very serious crippling issue and might be a bug, but perhaps someone has a solution.

Perhaps this thread should be in the troubleshooting section instead?