I'm currently troubleshooting some triggers I have set up for Zimbra, which is all set up very similarly to this article (http://www.denraf.be/content/zimbra-monitoring-zabbix)
However, this particular method seems to report a lot of false positives as the agent and the zimbra_status file don't work in sync with eachother, so the agent pulls a null value whenever the zimbra_status file is in the process of being overwritten by the bash script.
Kind of a vicious circle. Now I could rewrite the bash script to behave slightly differently, but for simplicity and time sake I was thinking more along the path of handling this via actions/triggers.
I'm still learning zabbix a bit so forgive my lack of knowledge in this area.
What I'd like to accomplish is essentially a trigger/action that would accomplish the following.
input from agent > check to see if false positive (run check 'x' times, if response is still 1/0 ) then > trigger action
Currently the trigger expression simply looks like this:
{server.mydomain.com:zimbra.antispam.last(0)}<1
Then the action has an escalation so it sends out a email every 10 minutes based on the 0/1 response from the trigger.
However, this particular method seems to report a lot of false positives as the agent and the zimbra_status file don't work in sync with eachother, so the agent pulls a null value whenever the zimbra_status file is in the process of being overwritten by the bash script.
Kind of a vicious circle. Now I could rewrite the bash script to behave slightly differently, but for simplicity and time sake I was thinking more along the path of handling this via actions/triggers.
I'm still learning zabbix a bit so forgive my lack of knowledge in this area.
What I'd like to accomplish is essentially a trigger/action that would accomplish the following.
input from agent > check to see if false positive (run check 'x' times, if response is still 1/0 ) then > trigger action
Currently the trigger expression simply looks like this:
{server.mydomain.com:zimbra.antispam.last(0)}<1
Then the action has an escalation so it sends out a email every 10 minutes based on the 0/1 response from the trigger.