Problem with simple checks triggers [bug?]
Hello.
I have defined following simple check to monitor if zabbix agent is running on port:
key:tcp,10050
type of information: numeric
And following trigger:
Now, i know that zabbix on server IS down and the latest data shows that status for server is 0 and it does not change when i look at the graph. This is correct behaviour
But trigger based on that value hops between TRUE and UNKNOWN about once per checking period ie. once it gets correct value and then something sets it to unknown. I guess it is do to with using simple checks together with agent checks, simple check works as intendent but when server checks for agent and finds it down, it changes status of host to unknown, even when other checks than agent are running fine against the server...
When i remove all other checks than simple checks from host, trigger stops hopping and show correct value.
I'm running server version 1.1beta7 with tcp,port patch installed on Fedora Core 3. Agent version is win32 1.1beta3.
Bug or expected behavior? If last, i suggest to change it, its kindda confusing
And not logical either...
I have defined following simple check to monitor if zabbix agent is running on port:
key:tcp,10050
type of information: numeric
And following trigger:
Code:
{win32.server:tcp,10050.last(0)}#1
But trigger based on that value hops between TRUE and UNKNOWN about once per checking period ie. once it gets correct value and then something sets it to unknown. I guess it is do to with using simple checks together with agent checks, simple check works as intendent but when server checks for agent and finds it down, it changes status of host to unknown, even when other checks than agent are running fine against the server...
When i remove all other checks than simple checks from host, trigger stops hopping and show correct value.
I'm running server version 1.1beta7 with tcp,port patch installed on Fedora Core 3. Agent version is win32 1.1beta3.
Bug or expected behavior? If last, i suggest to change it, its kindda confusing
And not logical either...
Comment