Hi,
I have the web monitoring enabled and have alerts (via e-mail) configured if a site goes down (using ZABBIX 1.4.5). It's all based on triggers, e.g.
{ZABBIX Server:web.test.fail[bar].last(0)}#0
...and works well indeed.
What I'm trying to achieve is to include actual failure error in the e-mail template. I've tried the following (expression -> result):
{TRIGGER.NAME}: {STATUS} -> [foo] bar is down: ON
{ITEM.LASTVALUE} -> 1
{{HOSTNAME}:{TRIGGER.KEY}.last(0)} -> 1
What I'm looking for is actual reason of why the page couldn't be accessed, something like:
Failed on "1" [1 of 1] Error: Page didn't match
which is displayed if I go to the Monitoring -> Web.
Why do I need this? It's because the trigger could fail for many reasons: HTTP didn't return 200 response, DNS couldn't resolve, was it a timeout, etc. I can only see the actual reason if I go straight to the website as another website check after a minute might clear it and the actual reason would left unknown.
Should this be possible, I think it would be a nice addition to the user manual as well.
Thanks in advance.
Regards,
Mindaugas
I have the web monitoring enabled and have alerts (via e-mail) configured if a site goes down (using ZABBIX 1.4.5). It's all based on triggers, e.g.
{ZABBIX Server:web.test.fail[bar].last(0)}#0
...and works well indeed.
What I'm trying to achieve is to include actual failure error in the e-mail template. I've tried the following (expression -> result):
{TRIGGER.NAME}: {STATUS} -> [foo] bar is down: ON
{ITEM.LASTVALUE} -> 1
{{HOSTNAME}:{TRIGGER.KEY}.last(0)} -> 1
What I'm looking for is actual reason of why the page couldn't be accessed, something like:
Failed on "1" [1 of 1] Error: Page didn't match
which is displayed if I go to the Monitoring -> Web.
Why do I need this? It's because the trigger could fail for many reasons: HTTP didn't return 200 response, DNS couldn't resolve, was it a timeout, etc. I can only see the actual reason if I go straight to the website as another website check after a minute might clear it and the actual reason would left unknown.
Should this be possible, I think it would be a nice addition to the user manual as well.
Thanks in advance.
Regards,
Mindaugas
Comment